service guide - ps-2.kev009.comps-2.kev009.com/rs6000/manuals/fibre/2102-f10-d00... · 1999. 12....

Fibre Channel RAID Storage Server andExpandable Storage Unit, IBM 2102Model F10 and Model D00

Service Guide

SY27-7604-02

IBM

Take Note!Before using this information and the product it supports, be sure to read the general information under “Notices” on page xv.

Second Edition (April 1999)

Publications are not stocked at the address given below. If you want additional IBM publications, ask your IBMrepresentative or write to the IBM branch office serving your locality.

A form for reader’s comments is provided at the back of this publication. If the form has been removed, address yourcomments to:

International Business Machines CorporationRCF Processing DepartmentDept G26/Bldg. 050-35600 Cottle RoadSAN JOSE, CA 95193-0001U.S.A.

You can also send your comments electronically to:

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

© Copyright International Business Machines Corporation 1999. All rights reserved.US Government Users Restricted Rights – Use duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . xvSafety and Environmental Notices . . . . . . . . . . . . . . . . . xv

Safety Notices . . . . . . . . . . . . . . . . . . . . . . . . xvEnvironmental Notices and Statements . . . . . . . . . . . . . . xvi

Electronic Emission Statements . . . . . . . . . . . . . . . . . . xviFederal Communications Commission (FCC) Statement . . . . . . . . xviIndustry Canada Compliance Statement . . . . . . . . . . . . . . xviiEuropean Community Compliance Statement . . . . . . . . . . . . xviiGermany Only . . . . . . . . . . . . . . . . . . . . . . . . xviiJapanese Voluntary Control Council for Interference (VCCI) Class A

Statement . . . . . . . . . . . . . . . . . . . . . . . . xviiiKorean Government Ministry of Communication (MOC) Statement . . . . xviiiTaiwan Class A Compliance Statement. . . . . . . . . . . . . . . xviii

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

IBM License Agreement for Machine Code . . . . . . . . . . . . . xxi

Statements of Limited Warranty . . . . . . . . . . . . . . . . . xxiiiProduction Status . . . . . . . . . . . . . . . . . . . . . . . xxiiiThe IBM Warranty for Machines . . . . . . . . . . . . . . . . . . xxiiiWarranty Service . . . . . . . . . . . . . . . . . . . . . . . . xxivExtent of Warranty . . . . . . . . . . . . . . . . . . . . . . . xxivLimitation of Liability . . . . . . . . . . . . . . . . . . . . . . xxv

About This Book . . . . . . . . . . . . . . . . . . . . . . . xxviiWho Should Use This Book . . . . . . . . . . . . . . . . . . . . xxviiRelated Publications . . . . . . . . . . . . . . . . . . . . . . xxviiWeb Site . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Part 1. Maintenance Starting Points . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 1. Maintenance Starting Points . . . . . . . . . . . . . . 32102 Fibre Channel RAID Storage Server Start Tables . . . . . . . . . . 4

Start Table A . . . . . . . . . . . . . . . . . . . . . . . . 4Start Table B . . . . . . . . . . . . . . . . . . . . . . . . 8Start Table C . . . . . . . . . . . . . . . . . . . . . . . . 11Start Table D . . . . . . . . . . . . . . . . . . . . . . . . 13

AIX Error Codes (SRNs) . . . . . . . . . . . . . . . . . . . . . 15The Error Code Table . . . . . . . . . . . . . . . . . . . . . 15Using the Error Code Table . . . . . . . . . . . . . . . . . . . 15Location Codes Displayed By Diagnostics . . . . . . . . . . . . . 31

Part 2. Installation and Removal . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 2. Installation And Removal Guide . . . . . . . . . . . . . 35Preparatory Tasks . . . . . . . . . . . . . . . . . . . . . . . 35

Tools and Equipment You May Need . . . . . . . . . . . . . . . 35About the Installation Procedure . . . . . . . . . . . . . . . . . 35

Preparing the Site . . . . . . . . . . . . . . . . . . . . . . . 36Floor Space . . . . . . . . . . . . . . . . . . . . . . . . 36

© Copyright IBM Corp. 1999 iii

Heating and Air Conditioning . . . . . . . . . . . . . . . . . . 38Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . 39Interface Connectors and Cables . . . . . . . . . . . . . . . . . 41

Preparing the Rackmount Cabinet . . . . . . . . . . . . . . . . . 43Cabinet Preparation Task List . . . . . . . . . . . . . . . . . . 43

Installing the Support Rails . . . . . . . . . . . . . . . . . . . . 44About Support Rails. . . . . . . . . . . . . . . . . . . . . . 44Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installing the Controller Module . . . . . . . . . . . . . . . . . . 45Tools and Equipment . . . . . . . . . . . . . . . . . . . . . 45Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 45

Installing the Drive Module . . . . . . . . . . . . . . . . . . . . 49Tools and Equipment . . . . . . . . . . . . . . . . . . . . . 49Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 49

Configuring the Controller Module . . . . . . . . . . . . . . . . . 54Completing the Installation . . . . . . . . . . . . . . . . . . . . 56

Start-up Notes . . . . . . . . . . . . . . . . . . . . . . . . 56Configuration Notes . . . . . . . . . . . . . . . . . . . . . . 56Starting Up the Subsystem . . . . . . . . . . . . . . . . . . . 56Verifying the Installation . . . . . . . . . . . . . . . . . . . . 58

Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . 59LVD-SCSI Drive Cable Routing Examples . . . . . . . . . . . . . . 59

Drive Cabling Example A . . . . . . . . . . . . . . . . . . . . 59Drive Cabling Example B . . . . . . . . . . . . . . . . . . . . 60Drive Cabling Example C. . . . . . . . . . . . . . . . . . . . 61Drive Cabling Example D. . . . . . . . . . . . . . . . . . . . 62Drive Cabling Example E . . . . . . . . . . . . . . . . . . . . 63Drive Cabling Example F . . . . . . . . . . . . . . . . . . . . 64

Part 3. Controller Module Service Guide . . . . . . . . . . . . . . . . . . . 67

Chapter 3. Getting Started . . . . . . . . . . . . . . . . . . . . 69Identifying the Parts. . . . . . . . . . . . . . . . . . . . . . . 69

Controller Module Cabinets . . . . . . . . . . . . . . . . . . . 69Removable Components . . . . . . . . . . . . . . . . . . . . 69Internal Components . . . . . . . . . . . . . . . . . . . . . 70

Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . 72Gaining Access to the Controls . . . . . . . . . . . . . . . . . 72Turning On the Power . . . . . . . . . . . . . . . . . . . . . 72Turning Off the Power . . . . . . . . . . . . . . . . . . . . . 74Restoring Power . . . . . . . . . . . . . . . . . . . . . . . 74Using the Status LEDs. . . . . . . . . . . . . . . . . . . . . 75

Instructions for Modifying the Controller Module . . . . . . . . . . . . 78Preparing to Move the Controller Module . . . . . . . . . . . . . . 79Removing and Installing FRUs . . . . . . . . . . . . . . . . . . 79Removing the Module from the Rackmount Cabinet . . . . . . . . . . 81Disassembling and Reassembling the Chassis . . . . . . . . . . . . 83

Chapter 4. Controllers . . . . . . . . . . . . . . . . . . . . . 87Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 87

General Description . . . . . . . . . . . . . . . . . . . . . . 87Identifying Interface Problems . . . . . . . . . . . . . . . . . . . 87

Types of Interface Problems. . . . . . . . . . . . . . . . . . . 87Hints for Troubleshooting Interface Problems . . . . . . . . . . . . 88

Controller FRU . . . . . . . . . . . . . . . . . . . . . . . . 89Controller Description . . . . . . . . . . . . . . . . . . . . . 89

iv IBM 2102 Model F10 and Model D00 Service Guide

Controller Specifications . . . . . . . . . . . . . . . . . . . . 91Controller Servicing Notes . . . . . . . . . . . . . . . . . . . 91Troubleshooting Controller Problems . . . . . . . . . . . . . . . 92Replacing a Failed Controller . . . . . . . . . . . . . . . . . . 93

Controller Backpanel . . . . . . . . . . . . . . . . . . . . . . 96Controller Backpanel Description . . . . . . . . . . . . . . . . . 96Controller Backpanel Specifications . . . . . . . . . . . . . . . . 97Controller Backpanel Servicing Notes . . . . . . . . . . . . . . . 97Troubleshooting Controller Backpanel Problems . . . . . . . . . . . 97Replacing a Failed Controller Backpanel . . . . . . . . . . . . . . 98

Chapter 5. Cooling System . . . . . . . . . . . . . . . . . . . 101Overview of Cooling System . . . . . . . . . . . . . . . . . . . 101

General Description . . . . . . . . . . . . . . . . . . . . . . 101Servicing the Cooling System . . . . . . . . . . . . . . . . . . . 101

Preserving Proper Air Flow . . . . . . . . . . . . . . . . . . . 102Determining Which Fan Failed . . . . . . . . . . . . . . . . . . 102

Controller Fan FRU . . . . . . . . . . . . . . . . . . . . . . . 103Controller Fan Description . . . . . . . . . . . . . . . . . . . 103Controller Fan Specifications . . . . . . . . . . . . . . . . . . 104Controller Fan Servicing Notes. . . . . . . . . . . . . . . . . . 105Troubleshooting Controller Fan Problems . . . . . . . . . . . . . . 105Replacing a Failed Controller Fan . . . . . . . . . . . . . . . . 106

Power Supply Fan FRU . . . . . . . . . . . . . . . . . . . . . 107Power Supply Fan Description . . . . . . . . . . . . . . . . . . 107Power Supply Fan . . . . . . . . . . . . . . . . . . . . . . 108Power Supply Fan Servicing Notes . . . . . . . . . . . . . . . . 109Troubleshooting Power Supply Fan Problems . . . . . . . . . . . . 109Replacing a Failed Power Supply Fan . . . . . . . . . . . . . . . 109

Chapter 6. Power System . . . . . . . . . . . . . . . . . . . . 111Overview of Power System . . . . . . . . . . . . . . . . . . . . 111

General Description . . . . . . . . . . . . . . . . . . . . . . 111Servicing the Power System . . . . . . . . . . . . . . . . . . . 111

Types of Power System Problems . . . . . . . . . . . . . . . . 112Hardware-Related Problems . . . . . . . . . . . . . . . . . . 112

Battery FRU . . . . . . . . . . . . . . . . . . . . . . . . . 112Battery Description . . . . . . . . . . . . . . . . . . . . . . 112Battery Specifications . . . . . . . . . . . . . . . . . . . . . 113Battery Servicing Notes . . . . . . . . . . . . . . . . . . . . 113Troubleshooting Battery Problems . . . . . . . . . . . . . . . . 114Checking the Battery Service Date . . . . . . . . . . . . . . . . 115Replacing the Battery FRU . . . . . . . . . . . . . . . . . . . 116

Power Supply FRU . . . . . . . . . . . . . . . . . . . . . . . 118Power Supply Description . . . . . . . . . . . . . . . . . . . 118Power Supply Specifications . . . . . . . . . . . . . . . . . . 119Power Supply Recovery Notes. . . . . . . . . . . . . . . . . . 119Troubleshooting Power Supply Problems . . . . . . . . . . . . . . 120Recovering from a Power Supply Shutdown . . . . . . . . . . . . . 121Replacing a Failed Power Supply. . . . . . . . . . . . . . . . . 122

Battery Harness . . . . . . . . . . . . . . . . . . . . . . . . 123Battery Harness Description. . . . . . . . . . . . . . . . . . . 123Battery Harness Specifications. . . . . . . . . . . . . . . . . . 124Battery Harness Servicing Notes . . . . . . . . . . . . . . . . . 124Troubleshooting Battery Harness Problems . . . . . . . . . . . . . 125Replacing the Battery Harness. . . . . . . . . . . . . . . . . . 125

Contents v

DC Power Harnesses . . . . . . . . . . . . . . . . . . . . . . 126DC Power Harness Description . . . . . . . . . . . . . . . . . 126DC Power Harness Specifications . . . . . . . . . . . . . . . . 127DC Power Harness Servicing Notes . . . . . . . . . . . . . . . . 127Troubleshooting DC Power Harness Problems . . . . . . . . . . . . 127Replacing the DC Power Harnesses. . . . . . . . . . . . . . . . 128

Power Interface Board . . . . . . . . . . . . . . . . . . . . . . 130Power Interface Board Description . . . . . . . . . . . . . . . . 130Power Interface Specifications . . . . . . . . . . . . . . . . . . 130Power Interface Board Servicing Notes . . . . . . . . . . . . . . 130Troubleshooting Power Interface Board Problems . . . . . . . . . . . 131Replacing a Controller Module Chassis . . . . . . . . . . . . . . 131

Chapter 7. Reference . . . . . . . . . . . . . . . . . . . . . . 133Troubleshooting Quick Reference. . . . . . . . . . . . . . . . . . 133

Controller and Interface Problems . . . . . . . . . . . . . . . . 133Cooling Problems . . . . . . . . . . . . . . . . . . . . . . 135Power Problems . . . . . . . . . . . . . . . . . . . . . . . 136

Part 4. Drive Module Service Guide . . . . . . . . . . . . . . . . . . . . . .139

Chapter 8. Getting Started with the Drive Module . . . . . . . . . . . 141What is the Drive Module? . . . . . . . . . . . . . . . . . . . . 141Basic Components . . . . . . . . . . . . . . . . . . . . . . . 142

Front View . . . . . . . . . . . . . . . . . . . . . . . . . 142Back View . . . . . . . . . . . . . . . . . . . . . . . . . 142

About the Drives . . . . . . . . . . . . . . . . . . . . . . . . 143Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . 143Drive FRUs . . . . . . . . . . . . . . . . . . . . . . . . . 144Drive Numbering . . . . . . . . . . . . . . . . . . . . . . . 144Drive Capacities . . . . . . . . . . . . . . . . . . . . . . . 145

About the SCSI Components . . . . . . . . . . . . . . . . . . . 146Environmental Services Monitor Board . . . . . . . . . . . . . . . 146Mid-Plane . . . . . . . . . . . . . . . . . . . . . . . . . 148Interface Cables . . . . . . . . . . . . . . . . . . . . . . . 149

About the Power System . . . . . . . . . . . . . . . . . . . . . 149Power Supply FRUs . . . . . . . . . . . . . . . . . . . . . 149

About the Cooling System . . . . . . . . . . . . . . . . . . . . 151Fan FRUs . . . . . . . . . . . . . . . . . . . . . . . . . 151

Moving The Drives . . . . . . . . . . . . . . . . . . . . . . . 151

Chapter 9. Operating the Drive Module . . . . . . . . . . . . . . . 153Basic Operation . . . . . . . . . . . . . . . . . . . . . . . . 153

Controls on the Front . . . . . . . . . . . . . . . . . . . . . 153Controls on the Back . . . . . . . . . . . . . . . . . . . . . 153Turn On the Power . . . . . . . . . . . . . . . . . . . . . . 153Turn Off the Power . . . . . . . . . . . . . . . . . . . . . . 154Perform an Emergency Shutdown . . . . . . . . . . . . . . . . 155Restore Power After an Emergency . . . . . . . . . . . . . . . . 156

Checking the Drive Module . . . . . . . . . . . . . . . . . . . . 156Status LEDs . . . . . . . . . . . . . . . . . . . . . . . . 156Check the Overall Hardware Status . . . . . . . . . . . . . . . . 156

Chapter 10. Servicing the Drives . . . . . . . . . . . . . . . . . 159Disk Drive Overview . . . . . . . . . . . . . . . . . . . . . . 159

General Notes . . . . . . . . . . . . . . . . . . . . . . . . 159

vi IBM 2102 Model F10 and Model D00 Service Guide

Drive Failure Notes . . . . . . . . . . . . . . . . . . . . . . 160Maintaining the Drives . . . . . . . . . . . . . . . . . . . . . . 160

Replace a Failed Drive . . . . . . . . . . . . . . . . . . . . 160Identify Other Drive-Related Problems . . . . . . . . . . . . . . . 164

Chapter 11. Servicing the SCSI Components . . . . . . . . . . . . 167SCSI Component Overview . . . . . . . . . . . . . . . . . . . . 167

Servicing SCSI Components . . . . . . . . . . . . . . . . . . 167Maintaining the SCSI Components . . . . . . . . . . . . . . . . . 168

Types of Interface Problems. . . . . . . . . . . . . . . . . . . 168Hints for Troubleshooting Interface Problems . . . . . . . . . . . . 169Replace a SCSI Interface Cable . . . . . . . . . . . . . . . . . 169Replace a Failed ESM FRU. . . . . . . . . . . . . . . . . . . 170Replace a Failed MidPlane . . . . . . . . . . . . . . . . . . . 173

Chapter 12. Servicing the Power System . . . . . . . . . . . . . . 179Power System Overview . . . . . . . . . . . . . . . . . . . . . 179

Power Supply Servicing Notes . . . . . . . . . . . . . . . . . . 179Power Supply Recovery Notes. . . . . . . . . . . . . . . . . . 179

Maintaining the Power System . . . . . . . . . . . . . . . . . . . 180Types of Power System Problems . . . . . . . . . . . . . . . . 180Recover from a Power Supply Shutdown . . . . . . . . . . . . . . 180Replace a Failed Power Supply . . . . . . . . . . . . . . . . . 183

Chapter 13. Servicing the Cooling System . . . . . . . . . . . . . 187Cooling System Overview . . . . . . . . . . . . . . . . . . . . 187

Fan Servicing Notes . . . . . . . . . . . . . . . . . . . . . 187Maintaining the Cooling Fans . . . . . . . . . . . . . . . . . . . 187

Replace a Failed Fan . . . . . . . . . . . . . . . . . . . . . 188

Chapter 14. Technical Reference . . . . . . . . . . . . . . . . . 191Technical Specifications . . . . . . . . . . . . . . . . . . . . . 191

Factory Settings . . . . . . . . . . . . . . . . . . . . . . . 191Hardware Features . . . . . . . . . . . . . . . . . . . . . . 192Software Features . . . . . . . . . . . . . . . . . . . . . . 192

Interface Connections and Cables . . . . . . . . . . . . . . . . . 193Drive Module Interface Connections . . . . . . . . . . . . . . . . 193Host SCSI Interface Connections . . . . . . . . . . . . . . . . . 193SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . 194Host SCSI Pin Assignments and Signals . . . . . . . . . . . . . . 194SCSI Drive Pin Assignments and Signals . . . . . . . . . . . . . . 195

Chapter 15. Quick References . . . . . . . . . . . . . . . . . . 197Drive Module Parts . . . . . . . . . . . . . . . . . . . . . . . 197Drive Module Troubleshooting Chart. . . . . . . . . . . . . . . . . 198

Part 5. Debugging Tools and Procedures . . . . . . . . . . . . . . . . . . .203

Chapter 16. RAID Manager for DOS . . . . . . . . . . . . . . . . 205What is RAID Manager for DOS?. . . . . . . . . . . . . . . . . . 205When to Use RAID Manager for DOS . . . . . . . . . . . . . . . . 205Menu Options Summary . . . . . . . . . . . . . . . . . . . . . 206Task Summary . . . . . . . . . . . . . . . . . . . . . . . . 208PC Requirements and Preparation Tasks . . . . . . . . . . . . . . . 208

PC Requirements . . . . . . . . . . . . . . . . . . . . . . 208Preparation Tasks . . . . . . . . . . . . . . . . . . . . . . 209

Contents vii

Changing DRM Boot Up Defaults (Floppy Drive and COM Port) . . . . . . 210Using DRM with a Monochrome Display . . . . . . . . . . . . . . . 210Connecting to the Controller Locally . . . . . . . . . . . . . . . . . 210Starting DRM . . . . . . . . . . . . . . . . . . . . . . . . . 211Verifying the Installation . . . . . . . . . . . . . . . . . . . . . 212Using the Array Configuration Editor (ACE) . . . . . . . . . . . . . . 212

Starting ACE . . . . . . . . . . . . . . . . . . . . . . . . 213The Logical Unit Window . . . . . . . . . . . . . . . . . . . . 214The Drive Window . . . . . . . . . . . . . . . . . . . . . . 216Navigating in ACE . . . . . . . . . . . . . . . . . . . . . . 221Identifying Drives and Logical Units . . . . . . . . . . . . . . . . 222Identify the Controller or Change the Name . . . . . . . . . . . . . 222Scan the Bus for Array Devices . . . . . . . . . . . . . . . . . 222Using the Array Monitor . . . . . . . . . . . . . . . . . . . . 223Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . 225Changing the Password . . . . . . . . . . . . . . . . . . . . 226Display and Set the Battery Age . . . . . . . . . . . . . . . . . 226Checking Array Status . . . . . . . . . . . . . . . . . . . . . 226

Chapter 17. Installing the Remote Support Feature . . . . . . . . . . 229Remote Support Attachment of the WTI Data Switch and Modem . . . . . . 229

Remote Support Feature Initial Installation . . . . . . . . . . . . . 229

Chapter 18. Drive Microcode Download . . . . . . . . . . . . . . 239Downloading Drive Microcode from Windows NT using DriveDload . . . . . 239

What is DriveDload? . . . . . . . . . . . . . . . . . . . . . 239When to Use DriveDload . . . . . . . . . . . . . . . . . . . . 239Installing DriveDload . . . . . . . . . . . . . . . . . . . . . 239Starting DriveDload . . . . . . . . . . . . . . . . . . . . . . 240Using DriveDload . . . . . . . . . . . . . . . . . . . . . . 240Drive Mode Page Download. . . . . . . . . . . . . . . . . . . 243

Downloading Drive Microcode from HP-UX or SUN Solaris Using drvDLoad . . 244What is drvDLoad? . . . . . . . . . . . . . . . . . . . . . . 244When to Use drvDLoad . . . . . . . . . . . . . . . . . . . . 244Installing drvDLoad . . . . . . . . . . . . . . . . . . . . . . 244Starting drvDLoad . . . . . . . . . . . . . . . . . . . . . . 245Using drvDLoad . . . . . . . . . . . . . . . . . . . . . . . 245

Downloading Drive Microcode From An AIX Host . . . . . . . . . . . . 246

Chapter 19. Controller Debug Shell . . . . . . . . . . . . . . . . 247Accessing the Controller Debug Shell . . . . . . . . . . . . . . . . 247Controller Debug Shell Commands . . . . . . . . . . . . . . . . . 248

Summary of Common Debug Shell Commands . . . . . . . . . . . 248

Part 6. Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251

Appendix A. AIX Code Information . . . . . . . . . . . . . . . . 2532102-F10 Error Log Sense Information. . . . . . . . . . . . . . . . 253Field Replaceable Unit (FRU) Codes . . . . . . . . . . . . . . . . 258Additional FRU Information . . . . . . . . . . . . . . . . . . . . 258Disk Array Errors . . . . . . . . . . . . . . . . . . . . . . . . 2602102 Array Additional Sense Codes And Qualifiers (ASC/ASQ) . . . . . . . 261

Appendix B. Safety Inspection Procedure . . . . . . . . . . . . . . 269

Appendix C. Safety Inspection Procedure in German . . . . . . . . . 273

viii IBM 2102 Model F10 and Model D00 Service Guide

Appendix D. Safety Inspection Procedure in Traditional Chinese . . . . . 277

Appendix E. Fibre Channel RAID Storage Server and Expandable StorageUnit Parts Catalog . . . . . . . . . . . . . . . . . . . . . . 281

2102 Model F10 Controller Module FRUs. . . . . . . . . . . . . . . 2822102 Model D00 Drive Module FRUs . . . . . . . . . . . . . . . . 286

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Readers’ Comments — We’d Like to Hear from You . . . . . . . . . . 309

Contents ix

x IBM 2102 Model F10 and Model D00 Service Guide

Figures

1. Controller Module Dimensions . . . . . . . . . . . . . . . . . 372. Dimensions of Drive Module . . . . . . . . . . . . . . . . . . 383. Interface Connections on Controller Module . . . . . . . . . . . . 414. Media Interface Adapter (MIA) . . . . . . . . . . . . . . . . . 425. Rackmount Cabinet . . . . . . . . . . . . . . . . . . . . . 436. Removable Covers on the Controller Module. . . . . . . . . . . . 467. Removing The FRUs . . . . . . . . . . . . . . . . . . . . 468. Removing The FRUs – cont.. . . . . . . . . . . . . . . . . . 479. Removing The FRUs – cont.. . . . . . . . . . . . . . . . . . 47

10. Chassis Mounting on Support Rails . . . . . . . . . . . . . . . 4811. Interface Connections on a Rackmount Controller Module . . . . . . . 4912. Removing the Drive Module FRUs . . . . . . . . . . . . . . . 5013. Removing the Drive Module FRUs – cont.. . . . . . . . . . . . . 5114. Tray ID and Option Switches . . . . . . . . . . . . . . . . . 5315. Connecting Interface Cables and Power Cords . . . . . . . . . . . 5416. Setting the Fibre Host IDs . . . . . . . . . . . . . . . . . . 5517. Controller Module Power Cords and Power Switches. . . . . . . . . 5718. Drive Module Power Switches . . . . . . . . . . . . . . . . . 5719. Rackmount Cabling to One Drive Module . . . . . . . . . . . . . 6020. Rackmount Cabling to Two Drive Modules . . . . . . . . . . . . 6121. Rackmount Cabling to Three Drive Modules . . . . . . . . . . . . 6222. Rackmount Cabling to Four Drive Modules . . . . . . . . . . . . 6323. Rackmount Cabling to Five Drive Modules . . . . . . . . . . . . 6424. Rackmount Cabling to Six Drive Modules . . . . . . . . . . . . . 6525. Rackmount Cabinet . . . . . . . . . . . . . . . . . . . . . 6926. Front View of Controller Module . . . . . . . . . . . . . . . . 7027. Back View of Controller Module . . . . . . . . . . . . . . . . 7028. Internal Components . . . . . . . . . . . . . . . . . . . . 7129. Internal Components – cont. . . . . . . . . . . . . . . . . . . 7130. Removable Cover on the Controller Module . . . . . . . . . . . . 7231. Controller Module Power Switches . . . . . . . . . . . . . . . 7332. LEDs on the Front . . . . . . . . . . . . . . . . . . . . . 7633. LEDs on the Back . . . . . . . . . . . . . . . . . . . . . 7834. Removing and Installing FRUs . . . . . . . . . . . . . . . . . 8035. Removing and Installing FRUs – cont. . . . . . . . . . . . . . . 8036. Removing and Installing FRUs – cont. . . . . . . . . . . . . . . 8137. Disconnecting Interface Cables. . . . . . . . . . . . . . . . . 8238. Removing and Installing the Chassis on Support Rails . . . . . . . . 8239. Removing and Replacing the Cover Plate . . . . . . . . . . . . . 8340. Removing Screws, Harnesses, and Power Supply Assembly . . . . . . 8441. DC Battery and Power Harness Connections . . . . . . . . . . . 8542. Removing the Controller Card Cage . . . . . . . . . . . . . . . 8543. Controller FRUs in Controller Module . . . . . . . . . . . . . . 8744. Controller FRU, Slots and LEDs . . . . . . . . . . . . . . . . 8945. Controller FRU, Slots and LEDs – cont. . . . . . . . . . . . . . 9046. LEDs on Front Covers . . . . . . . . . . . . . . . . . . . . 9347. Removing and Installing a Controller FRU. . . . . . . . . . . . . 9548. Controller Card Cage . . . . . . . . . . . . . . . . . . . . 9649. Controller Module Cooling System . . . . . . . . . . . . . . . 10150. Air Flow through Chassis . . . . . . . . . . . . . . . . . . . 10251. Controller Module Fan Fault LEDs . . . . . . . . . . . . . . . 10352. Controller Fan FRU and Status LEDs . . . . . . . . . . . . . . 10453. Removing and Installing a Controller Fan . . . . . . . . . . . . . 107

© Copyright IBM Corp. 1999 xi

54. Power Supply Fan FRU . . . . . . . . . . . . . . . . . . . 10855. Removing and Installing a Power Supply Fan FRU . . . . . . . . . 11056. Controller Module Power System FRUs . . . . . . . . . . . . . 11157. Battery FRU. . . . . . . . . . . . . . . . . . . . . . . . 11358. Removing and Replacing a Front Cover . . . . . . . . . . . . . 11559. Battery FRU Service Label . . . . . . . . . . . . . . . . . . 11660. Removing and Installing the Battery FRU . . . . . . . . . . . . . 11761. Power Supply FRU . . . . . . . . . . . . . . . . . . . . . 11962. Fault Indicators for a Failed Power Supply . . . . . . . . . . . . 12263. Turning Off the Power and Unplugging the Power Cord . . . . . . . . 12364. Removing and Installing a Power Supply FRU . . . . . . . . . . . 12365. Battery Harness . . . . . . . . . . . . . . . . . . . . . . 12466. Removing and Installing a Battery Harness . . . . . . . . . . . . 12667. DC Power Harnesses . . . . . . . . . . . . . . . . . . . . 12768. Reconnecting the DC Power Harnesses . . . . . . . . . . . . . 12969. Power Supply Assembly . . . . . . . . . . . . . . . . . . . 13070. Drive Module . . . . . . . . . . . . . . . . . . . . . . . 14171. Front Views of the Drive Module . . . . . . . . . . . . . . . . 14272. Back View of the Drive Module . . . . . . . . . . . . . . . . . 14373. Drive LEDs . . . . . . . . . . . . . . . . . . . . . . . . 14474. Drive FRU . . . . . . . . . . . . . . . . . . . . . . . . 14475. Drive Channel and SCSI ID Numbering. . . . . . . . . . . . . . 14576. ESM FRU . . . . . . . . . . . . . . . . . . . . . . . . 14677. ESM Board Connectors, Switches, and LEDs . . . . . . . . . . . 14778. Location of Mid-Plane . . . . . . . . . . . . . . . . . . . . 14979. Power Supply FRU . . . . . . . . . . . . . . . . . . . . . 15080. Fan FRU . . . . . . . . . . . . . . . . . . . . . . . . . 15181. Power Cords and Switches . . . . . . . . . . . . . . . . . . 15482. Drive LEDs on the Front Panel . . . . . . . . . . . . . . . . . 15783. LEDs on Drive Module with ESM Board . . . . . . . . . . . . . 15884. Drive FRU and Front Panel LEDs . . . . . . . . . . . . . . . . 16285. Removing/Installing Drive FRUs . . . . . . . . . . . . . . . . 16386. Amber Fault LEDs (Rackmount) . . . . . . . . . . . . . . . . 17187. Power Switches, Power Cords, and SCSI Interface Cables . . . . . . 17288. Removing/Installing an ESM FRU . . . . . . . . . . . . . . . . 17389. Power Switches, Power Cords, and SCSI Cables . . . . . . . . . . 17590. Removing/Installing Power Supplies and Interface FRUs . . . . . . . 17591. Removing/Installing Drive and Fan FRUs . . . . . . . . . . . . . 17692. Rear Mounting Screws . . . . . . . . . . . . . . . . . . . . 17793. Front Mounting Screws. . . . . . . . . . . . . . . . . . . . 17794. Fault LEDs on the Back of the Drive Module . . . . . . . . . . . . 18195. Fault LEDs on the Back of the Drive Module . . . . . . . . . . . . 18496. Power Switches and Power Cords . . . . . . . . . . . . . . . 18597. Removing/Installing a Power Supply FRU . . . . . . . . . . . . . 18698. Fault LEDs on the Back of the Drive Module . . . . . . . . . . . . 18999. Removing/Installing a Fan FRU . . . . . . . . . . . . . . . . 190

100. RAID Manager for DOS Main Menu . . . . . . . . . . . . . . . 212101. The Array Configuration Editor (ACE) Display . . . . . . . . . . . 213102. The Logical Unit window . . . . . . . . . . . . . . . . . . . 214103. The Logical Unit Status Display . . . . . . . . . . . . . . . . 215104. The Drive window . . . . . . . . . . . . . . . . . . . . . 217105. The Drive Matrix . . . . . . . . . . . . . . . . . . . . . . 218106. Device Drawer with Single Drive Bus (Bridge Disable OFF) . . . . . . 218107. Device Drawer with 2 Drive Buses (Bridge Disable ON). . . . . . . . 219108. Attachment of the Modem and WTI Switch to a IBM 2102 F10 Fibre

Channel Storage Server . . . . . . . . . . . . . . . . . . . 229

xii IBM 2102 Model F10 and Model D00 Service Guide

109. Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . 231110. Port Configuration Menu . . . . . . . . . . . . . . . . . . . 232111. Port Configuration Menu . . . . . . . . . . . . . . . . . . . 233112. Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . 237113. DriveDload Main Menu . . . . . . . . . . . . . . . . . . . . 241114. 2102 Model F10 Controller Module FRUs . . . . . . . . . . . . . 282115. 2102 Model F10 Controller Module FRUs – cont. . . . . . . . . . . 283116. 2102 Model F10 Controller Module FRUs – cont. . . . . . . . . . . 284117. 2102 Model D00 Drive Module FRUs . . . . . . . . . . . . . . 286

Figures xiii

xiv IBM 2102 Model F10 and Model D00 Service Guide

Notices

References in this publication to IBM products, programs, or services do not implythat IBM intends to make these available in all countries in which IBM operates. Anyreference to an IBM product, program, or service is not intended to state or implythat only that IBM product, program, or service may be used. Subject to IBM’s validintellectual property or other legally protected rights, any functionally equivalentproduct, program, or service, may be used instead of the IBM product, program, orservice. The evaluation and verification of operation in conjunction with otherproducts, except those expressly designated by IBM, are the responsibility of theuser.

IBM may have patents or pending patent applications covering subject matter in thisdocument. The furnishing of this document does not give you any license to thesepatents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

Read Before UsingIMPORTANT

YOU ACCEPT THE TERMS OF THIS IBM LICENSE AGREEMENT FORMACHINE CODE BY YOUR USE OF THE HARDWARE PRODUCT ORMACHINE CODE. PLEASE READ THE AGREEMENT CONTAINED IN THISBOOK BEFORE USING THE HARDWARE PRODUCT. SEE “IBM LicenseAgreement for Machine Code” on page xxi.

Safety and Environmental Notices

This section contains information about:

v Safety notices used in this guide

v Environmental notices and statements for this product

Safety Notices

Note: For a translation of the danger and caution notices, see Translated SafetyNotices for Open Attachment, GC26-7246.

Definitions of Safety Notices

DANGER

A danger notice indicates the presence of a hazard that has the potential ofcausing death or serious personal injury.

CAUTION:A caution notice indicates the presence of a hazard that has the potential ofcausing minor or moderate personal injury.

© Copyright IBM Corp. 1999 xv

CAUTION:The drawer weighs approximately 25 kg (55 lb) with no devices installed. Donot try to lift it by yourself. Ask another service representative for assistance.

CAUTION:Energy hazard, remove power before servicing.

CAUTION:This unit weighs between 18 kg (39.7 pounds) and 32 kg (70.5 pounds). Twopersons are required to safely move it. Using less than two persons to moveit can result in injury.

Attention: An attention notice indicates the possibility of damage to a program,device, system or data.

Translations of the Safety Inspection Procedure

See “Appendix C. Safety Inspection Procedure in German” on page 273 and“Appendix D. Safety Inspection Procedure in Traditional Chinese” on page 277 forthe German and Chinese translations of “Appendix B. Safety Inspection Procedure”on page 269.

Environmental Notices and Statements

Product Disposal

This product contains a SEALED LEAD ACID BATTERY. When the batteryassembly is replaced, the used battery assembly must be returned to IBM forproper disposal.

Product Recycling

This unit contains recyclable materials. These materials should be recycled whereprocessing sites are available and according to local regulations. In some areasIBM provides a product take-back program that ensures proper handling of theproduct. Contact your IBM representative for more information.

Electronic Emission Statements

This section gives the electronic emission notices or statements for the UnitedStates and other countries.

Federal Communications Commission (FCC) Statement

This equipment has been tested and found to comply with the limits for a Class Adigital device, pursuant to Part 15 of the FCC Rules. These limits are designed toprovide reasonable protection against harmful interference when the equipment isoperated in a commercial environment. This equipment generates, uses, and canradiate radio frequency energy and, if not installed and used in accordance with theinstruction manual, may cause harmful interference to radio communications.Operation of this equipment in a residential area is likely to cause harmfulinterference, in which case the user will be required to correct the interference athis own expense.

xvi IBM 2102 Model F10 and Model D00 Service Guide

Properly shielded and grounded cables and connectors must be used in order tomeet FCC emission limits. IBM is not responsible for any radio or televisioninterference caused by using other than recommended cables and connectors or byunauthorized changes or modifications to this equipment. Unauthorized changes ormodifications could void the user’s authority to operate the equipment.

This device complies with Part 15 of the FCC Rules. Operation is subject to thefollowing two conditions: (1) this device may not cause harmful interference, and (2)this device must accept any interference received, including interference that maycause undesired operation.

Industry Canada Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d’Industrie Canada: Cet appareilnumérique de la classe A est conform à la norme NMB-003 du Canada.

European Community Compliance Statement

This product is in conformity with the protection requirements of EC CouncilDirective 89/336/EEC on the approximation of the laws of the Member Statesrelating to electromagnetic compatibility. IBM cannot accept responsibility for anyfailure to satisfy the protection requirements resulting from a non-recommendedmodification of the product, including the fitting of non-IBM option cards.

Germany Only

Zulassungsbescheinigung laut Gesetz ueber die elektromagnetischeVertraeglichkeit von Geraeten (EMVG) vom 30. August 1995 .

Dieses Geraet ist berechtigt, in Uebereinstimmung mit dem deutschen EMVG dasEG-Konformitaetszeichen - CE - zu fuehren.

Der Aussteller der Konformitaetserklaeung ist die IBM Deutschland.

Informationen in Hinsicht EMVG Paragraph 3 Abs. (2) 2:Das Geraet erfuellt die Schutzanforderungen nach EN 50082-1 undEN 55022 Klasse A.

EN 55022 Klasse A Geraete beduerfen folgender Hinweise:

Nach dem EMVG:"Geraete duerfen an Orten, fuer die sienicht ausreichend entstoertsind, nur mit besonderer Genehmigung des Bundesministeriumsfuer Post und Telekommunikation oder des Bundesamtes fuer Post undTelekommunikationbetrieben werden. Die Genehmigung wird erteilt, wenn keineelektromagnetischen Stoerungen zu erwarten sind." (Auszug aus demEMVG, Paragraph 3, Abs.4)

Dieses Genehmigungsverfahren ist nach Paragraph 9 EMVG in Verbindungmit der entsprechenden Kostenverordnung (Amtsblatt 14/93)kostenpflichtig.

Nach der EN 55022:

Notices xvii

"Dies ist eine Einrichtung der Klasse A. Diese Einrichtung kann imWohnbereich Funkstoerungen verursachen. in diesem Fall kann vomBetreiber verlangt werden, angemessene Massnahmen durchzufuehrenund dafuer aufzukommen."

Anmerkung:Um die Einhaltung des EMVG sicherzustellen, sind die Geraete wie in denHandbuechern angegeben zu installieren und zu betreiben.

Japanese Voluntary Control Council for Interference (VCCI) Class AStatement

Korean Government Ministry of Communication (MOC) Statement

Please note that this device has been approved for business purposes with regardto electromagnetic interference. If you find this is not suitable for your use, you mayexchange it for one with a non-business purpose.

Taiwan Class A Compliance Statement

Trademarks

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

IBM

Seascape

StorWatch

HP-UX and Hewlett-Packard are trademarks of Hewlett-Packard Company.

Sun, SPARC, SunOS, and Solaris, are trademarks of Sun Microsystems, Inc.

xviii IBM 2102 Model F10 and Model D00 Service Guide

Windows NT and Alpha Windows NT are trademarks of Microsoft Corporation.

UNIX is a registered trademark in the United States and other countries licensedexclusively through X/Open Company Limited.

Other company, product, or service names, may be trademarks or service marks ofothers.

Notices xix

xx IBM 2102 Model F10 and Model D00 Service Guide

IBM License Agreement for Machine Code

Regardless of how you acquire (electronically, preloaded, on media or otherwise)BIOS, Utilities, Diagnostics, Device Drivers or Microcode (collectively called“Machine Code”), you accept the terms of this Agreement by your initial use of aMachine or Machine Code. The term “Machine” means an IBM machine, itsfeatures, conversions, upgrades, elements or accessories, or any combination ofthem. Acceptance of these license terms authorizes you to use Machine Code withthe specific product for which it is provided.

International Business Machines Corporation or one of its subsidiaries (“IBM”), or anIBM supplier, owns copyrights in Machine Code.

IBM grants you a nonexclusive license to use Machine Code only in conjunctionwith a Machine. As the rightful possessor of a Machine, you may make areasonable number of copies of Machine Code as necessary for backup,configuration, and restoration of the Machine. You must reproduce the copyrightnotice and any other legend of ownership on each copy of Machine Code youmake.

You may transfer possession of Machine Code and its media to another party onlywith the transfer of the Machine on which the Machine Code is used. If you do so,you must give the other party a copy of these terms and provide all userdocumentation to that party. When you do so, you must destroy all your copies ofMachine Code.

Your license for Machine Code terminates when you no longer rightfully possess theMachine.

No other rights under this license are granted.

You may not, for example, do any of the following:

1. otherwise copy, display, transfer, adapt, modify, or distribute in any form,Machine Code, except as IBM may authorize in a Machine’s userdocumentation.

2. reverse assemble, reverse compile, or otherwise translate the Machine Code,unless expressly permitted by applicable law without the possibility ofcontractual waiver;

3. sublicense or assign the license for the Machine Code; or

4. lease the Machine Code or any copy of it.

The terms of IBM’s Machine warranty, which is incorporated into this Agreement byreference, apply to Machine Code. Please refer to that warranty for any questionsor claims regarding performance or liability for Machine Code.

© Copyright IBM Corp. 1999 xxi

xxii IBM 2102 Model F10 and Model D00 Service Guide

Statements of Limited WarrantyInternational Business Machines Corporation

Armonk, New York, 10504

The warranties provided by IBM in this Statement of Limited Warranty1apply only toMachines you originally purchase for your use, and not for resale, from IBM or yourreseller. The term “Machine” means an IBM machine, its features, conversions,upgrades, elements, or accessories, or any combination of them.

Unless IBM specifies otherwise, the following warranties apply only in the countrywhere you acquire the Machine. If you have any questions, contact IBM or yourreseller.

Machine: IBM Fibre Channel RAID Storage Server andExpandable Storage Unit

2102 Model F10 and 2102 Model D00

Warranty Period: One Year*

* Contact your place of purchase for warranty service information.

Production Status

Each Machine is manufactured from new parts, or new and used parts. In somecases, the Machine may not be new and may have been previously installed.Regardless of the Machine’s production status, IBM’s warranty terms apply.

The IBM Warranty for Machines

IBM warrants that each Machine 1) is free from defects in materials andworkmanship and 2) conforms to IBM’s Official Published Specifications. Thewarranty period for a Machine is a specified, fixed period commencing on its Dateof Installation. The date on your receipt is the Date of Installation, unless IBM oryour reseller informs you otherwise.

During the warranty period IBM or your reseller, if authorized by IBM, will providewarranty service under the type of service designated for the Machine and willmanage and install engineering changes that apply to the Machine.

For IBM or your reseller to provide warranty service for a feature, conversion, orupgrade, IBM or your reseller may require that the Machine on which it is installedbe 1) for certain Machines, the designated, serial-numbered Machine and 2) at anengineering-change level compatible with the feature, conversion, or upgrade. Manyof these transactions involve the removal of parts and their return to IBM. Yourepresent that all removed parts are genuine and unaltered. A part that replaces aremoved part will assume the warranty service status of the replaced part.

If a Machine does not function as warranted during the warranty period, IBM or yourreseller will repair it or replace it with one that is at least functionally equivalent,without charge. The replacement may not be new, but will be in good working order.

1. Form Z125-4753

© Copyright IBM Corp. 1999 xxiii

If IBM or your reseller is unable to repair or replace the Machine, you may return itto your place of purchase and your money will be refunded.

If you transfer a Machine to another user, warranty service is available to that userfor the remainder of the warranty period. You should give your proof of purchaseand this Statement to that user. However, for Machines which have a lifetimewarranty, this warranty is not transferable.

Warranty Service

To obtain warranty service for the Machine, you should contact your reseller or callIBM. In the United States, call IBM at 1-800-IBM-SERV (426-7378) In Canada, callIBM at 1-800-465-6666. You may be required to present proof of purchase.

IBM or your reseller will provide certain types of repair and exchange service, eitherat your location or at IBM’s or your reseller’s service center, to restore a Machine togood working order.

When a type of service involves the exchange of a Machine or part, the item IBM oryour reseller replaces becomes its property and the replacement becomes yours.You represent that all removed items are genuine and unaltered. The replacementmay not be new, but will be in good working order and at least functionallyequivalent to the item replaced. The replacement assumes the warranty servicestatus of the replaced item. Before IBM or your reseller exchanges a Machine orpart, you agree to remove all features, parts, options, alterations, and attachmentsnot under warranty service. You also agree to ensure that the Machine is free ofany legal obligations or restrictions that prevent its exchange.

You agree to:

1. obtain authorization from the owner to have IBM or your reseller service aMachine that you do not own; and

2. where applicable, before service is provided:

a. follow the problem determination, problem analysis, and service requestprocedures that IBM or your reseller provide,

b. secure all programs, data, and funds contained in a Machine, and

c. inform IBM or your reseller of changes in a Machine’s location.

IBM is responsible for loss of, or damage to, your Machine while it is 1) in IBM’spossession or 2) in transit in those cases where IBM is responsible for thetransportation charges.

Extent of Warranty

IBM does not warrant uninterrupted or error-free operation of a Machine.

The warranties may be voided by misuse, accident, modification, unsuitablephysical or operating environment, improper maintenance by you, removal oralteration of Machine or parts identification labels, or failure caused by a product forwhich IBM is not responsible.

THESE WARRANTIES REPLACE ALL OTHER WARRANTIES OR CONDITIONS,EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OR CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A

xxiv IBM 2102 Model F10 and Model D00 Service Guide

PARTICULAR PURPOSE. THESE WARRANTIES GIVE YOU SPECIFIC LEGALRIGHTS AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROMJURISDICTION TO JURISDICTION. SOME JURISDICTIONS DO NOT ALLOWTHE EXCLUSION OR LIMITATION OF EXPRESS OR IMPLIED WARRANTIES, SOTHE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TO YOU. IN THATEVENT SUCH WARRANTIES ARE LIMITED IN DURATION TO THE WARRANTYPERIOD. NO WARRANTIES APPLY AFTER THAT PERIOD.

Limitation of Liability

Circumstances may arise where, because of a default on IBM’s part or other liabilityyou are entitled to recover damages from IBM. In each such instance, regardless ofthe basis on which you are entitled to claim damages from IBM (includingfundamental breach, negligence, misrepresentation, or other contract or tort claim),IBM is liable only for:

1. damages for bodily injury (including death) and damage to real property andtangible personal property; and

2. the amount of any other actual direct damages or loss, up to the greater of U.S.$100,000 or the charges (if recurring, 12 months’ charges apply) for theMachine that is the subject of the claim.

UNDER NO CIRCUMSTANCES IS IBM LIABLE FOR ANY OF THE FOLLOWING:1) THIRD-PARTY CLAIMS AGAINST YOU FOR LOSSES OR DAMAGES (OTHERTHAN THOSE UNDER THE FIRST ITEM LISTED ABOVE); 2) LOSS OF, ORDAMAGE TO, YOUR RECORDS OR DATA; OR 3) SPECIAL, INCIDENTAL, ORINDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES(INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM OR YOUR RESELLERIS INFORMED OF THEIR POSSIBILITY. SOME JURISDICTIONS DO NOT ALLOWTHE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIALDAMAGES, SO THE ABOVE EXCLUSION OR LIMITATION MAY NOT APPLY TOYOU.

Statements of Limited Warranty xxv

xxvi IBM 2102 Model F10 and Model D00 Service Guide

About This Book

This book provides the information for servicing the IBM Fibre Channel RAIDStorage Server with the Expandable Storage Unit.

Who Should Use This Book

This publication is for Service Representatives who are installing and maintainingthe 2102 subsystem.

Related Publications

Additional information that is related to the subsystem is available in the followingpublications:

v Seascape Solution Rack, Installation and Service Guide, IBM 2101 Model 100,SY27-7606

v Fibre Channel RAID Storage Server, Introduction and Planning Guide, IBM 2102,GC26-7281

v Fibre Channel Storage Manager, Installation Guide for Microsoft Windows NT,SC26-7283

v StorWatch Fibre Channel RAID Specialist, Installation Guide for MicrosoftWindows NT and Windows 95, SC26-7284

v Fibre Channel Storage Manager and StorWatch Fibre Channel RAID Specialist,User’s Guide, SC26-7285

v Fibre Channel Storage Manager, Installation Guide for Sun Solaris OperatingSystem, SC26-7286

v Fibre Channel Storage Manager, Installation Guide for Hewlett Packard HP-UXOperating System, SC26-7287

v Fibre Channel RAID Storage Server and Expandable Storage Unit, User’s Guide,IBM 2102 Model F10 and Model D00, SC26-7288

v Fibre Channel Storage Hub, Installation, Service, and User’s Guide, IBM 2103Model H07, SC26-7289

v Fibre Channel Storage Manager, Installation and User’s Guide for the AIXOperating System, SC26-7290

v Diagnostic Information for Multiple Bus Systems, SA38-0509

Additional publications are available for purchase from IBM. For a list of publicationsavailable in your country:

v In the U.S. and Puerto Rico, call 1–800–426–7282.

v In the United Kingdom, call 01705–565000 or 0161–9056001.

v In Canada, call 1–800–465–1234.

v In other countries, contact the IBM support organization that services your area,your IBM marketing representative, or your IBM reseller.

Web Site

For more Fibre Channel Storage information, go tohttp://www.ibm.com/storage/fcss on the World Wide Web.

© Copyright IBM Corp. 1999 xxvii

xxviii IBM 2102 Model F10 and Model D00 Service Guide

Part 1. Maintenance Starting Points

© Copyright IBM Corp. 1999 1

2 IBM 2102 Model F10 and Model D00 Service Guide

Chapter 1. Maintenance Starting Points

The following four tables contain pointers into the 2102 subsystem maintenancepackage. Before using the tables, be sure to consult the Installation and/or User’sGuide for the storage management software specific to the operating system beingused. In many cases, these Guides contain procedures for analyzing and repairingproblems from the host that provide better isolation and the most up-to-daterecovery steps. Throughout this guide, the term ″storage management software″ isused generically to refer to the Fibre Channel Storage Manager software and itsrelated components running on a Windows NT, SUN Solaris, HP-UX or AIX hostplatform.

v For subsystems attached to a Windows NT host, refer to Fibre Channel StorageManager and StorWatch Fibre Channel RAID Specialist, User’s Guide,SC26-7285 and Fibre Channel Storage Manager, Installation Guide for MicrosoftWindows NT, SC26-7283.

v For subsystems attached to an HP-UX host, refer to Fibre Channel StorageManager and StorWatch Fibre Channel RAID Specialist, User’s Guide,SC26-7285 and Fibre Channel Storage Manager, Installation Guide for HewlettPackard HP-UX Operating System, SC26-7287.

v For subsystems attached to a SUN Solaris host, refer to Fibre Channel StorageManager and StorWatch Fibre Channel RAID Specialist, User’s Guide,SC26-7285 and Fibre Channel Storage Manager, Installation Guide for SunSolaris Operating System, SC26-7286.

v For subsystems attached to an AIX host, refer to Fibre Channel StorageManager, Installation and User’s Guide for the AIX Operating System,SC26-7290.

v For subsystems using a networked storage management station runningStorWatch Fibre Channel RAID Specialist, refer to Fibre Channel StorageManager and StorWatch Fibre Channel RAID Specialist, User’s Guide,SC26-7285 and StorWatch Fibre Channel RAID Specialist, Installation Guide forMicrosoft Windows NT and Windows 95, SC26-7284.

If you are unable to resolve the problem using the software guides or you cannotfind the appropriate information, then use these START tables. To use the tables,find the reason you are here in the left column and then perform the action in theright column.

After completing a recovery procedure (especially hardware replacement), youshould verify the subsystem status using the host software:

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then run the Recovery Guru to verify that the subsystem is operatingproperly. Refer to Fibre Channel Storage Manager and StorWatch Fibre ChannelRAID Specialist, User’s Guide, SC26-7285.

v If the subsystem is attached to an AIX host, then run the Advanced Diagnosticsin System Verification mode from the diagnostic interface (type ″diag″ from thecommand prompt) to verify that the subsystem is operating properly. Refer toFibre Channel Storage Manager, Installation and User’s Guide for the AIXOperating System, SC26-7290 and Diagnostic Information for Multiple BusSystems, SA38-0509 for more information (refer to MAP 0410 for returning thecustomer to normal operation).


2102 Fibre Channel RAID Storage Server Start Tables

Start Table ATable 1. 2102 Fibre Channel RAID Storage Server Start Table A

If you are here for thisreason...

...Then perform this action

Running diagnostics from anAIX host resulted in a six digitService Request Number/ErrorCode

Go to “AIX Error Codes (SRNs)” on page 15.


Table 1. 2102 Fibre Channel RAID Storage Server Start Table A (continued)



v A check light is active on asubsystem component

v A problem occurred duringan installation procedure

v The host software indicatedthat a problem occurredwithin the RAID arraysubsystem

v The customer observed aproblem that was notdetected or reported by thehost system

v You suspect a problemwithin the RAID arraysubsystem

Controller:

1. If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then run the Recovery Guru from the host system and follow therecovery procedures given. Refer to Fibre Channel Storage Manager andStorWatch Fibre Channel RAID Specialist, User’s Guide, SC26-7285.

2. If the subsystem is attached to an AIX host, then run Advanced Diagnostics inProblem Determination mode from the diagnostic interface (type ″diag″ from thecommand prompt). If the diagnostics return an error code for the 2102subsystem, then go to “AIX Error Codes (SRNs)” on page 15 and follow theinstructions for the error code generated. Once the problem has been addressed,rerun the AIX Advanced Diagnostics in System Verification mode to verify therepair. Refer to Fibre Channel Storage Manager, Installation and User’s Guide forthe AIX Operating System, SC26-7290 and Diagnostic Information for MultipleBus Systems, SA38-0509 (MAP 0410) for more information.

3. If you don’t have access to the host system or the host system does not providea recovery procedure or error code, then follow these steps in order:

a. Go to “Troubleshooting Controller Problems” on page 92 and follow theprocedure for the matching symptoms. If no symptoms match, go to the nextstep.

b. Go to “Troubleshooting Controller Fan Problems” on page 105 and follow theprocedure for the matching symptoms. If no symptoms match, go to the nextstep.

c. Go to “Identifying Interface Problems” on page 87 and follow the procedure fordebugging interface problems. If this does not fix the problem, go to the nextstep.

d. Go to “Troubleshooting Power Supply Problems” on page 120 and follow theprocedure for the matching symptoms. If no symptoms match, go to the nextstep.

e. Go to “Troubleshooting Battery Problems” on page 114 and follow theprocedure for the matching symptoms. If no symptoms match, go to the nextstep.

f. Go to “Troubleshooting Controller Backpanel Problems” on page 97 and followthe procedure for the matching symptoms. If no symptoms match, go to thenext step.

g. Go to “Troubleshooting Battery Harness Problems” on page 125 and followthe procedure for the matching symptoms. If no symptoms match, go to thenext step.

h. Go to “Troubleshooting DC Power Harness Problems” on page 127 and followthe procedure for the matching symptoms. If no symptoms match, go to thenext step.

i. Go to “Troubleshooting Power Interface Board Problems” on page 131 andfollow the procedure for the matching symptoms. If no symptoms match, go tothe next step.

j. Call your next level of support.

Chapter 1. Maintenance Starting Points 5




Continued from page 5. Device Drawer:

1. If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then run the Recovery Guru from the host system and follow therecovery procedures given. Refer to Fibre Channel Storage Manager andStorWatch Fibre Channel RAID Specialist, User’s Guide, SC26-7285.



a. Go to “Maintaining the Drives” on page 160 and follow the problemidentification procedures given. If this does not fix the problem, go to the nextstep.

b. Go to “Identify Other Drive-Related Problems” on page 164 and follow theproblem identification procedures given. If this does not fix the problem, go tothe next step.

c. Go to “Maintaining the SCSI Components” on page 168 and follow theproblem identification procedures given. If this does not fix the problem, go tothe next step.

d. Go to “Maintaining the Power System” on page 180 and follow the problemidentification procedures given. If this does not fix the problem, go to the nextstep.

e. Go to “Drive Module Troubleshooting Chart” on page 198 and follow theproblem identification procedures given. If this does not fix the problem, go tothe next step.

f. Call your next level of support.





Continued from page 5. Hub:

1. If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then run the Recovery Guru from the host system and follow therecovery procedures given. Refer to the Fibre Channel Storage Manager andStorWatch Fibre Channel RAID Specialist, User’s Guide, SC26-7285.



a. Go to ″Troubleshooting″ in Fibre Channel Storage Hub, Installation, Service,and User’s Guide, IBM 2103 Model H07, SC26-7289 and follow the problemidentification procedures given. If this does not fix the problem, go to the nextstep.

b. Go to ″Connect the Cables″ in Fibre Channel Storage Hub, Installation,Service, and User’s Guide, IBM 2103 Model H07, SC26-7289 and follow theproblem identification procedures given. If this does not fix the problem, go tothe next step.

c. Call your next level of support.

Rack:

Go to Seascape Solution Rack, Installation and Service Guide, IBM 2101 Model 100,SY27-7606 and follow the appropriate procedure for debugging rack problems. If youcannot fix the problem following the procedures in Seascape Solution Rack,Installation and Service Guide, IBM 2101 Model 100, SY27-7606, then call your nextlevel of support.


Start Table BTable 2. 2102 Fibre Channel RAID Storage Server Start Table B



Replace FRUs in the ControllerModule Controller Card Go to “Replacing a Failed Controller” on page 93

Battery Go to “Replacing the Battery FRU” on page 116

Backpanel Go to “Replacing a Failed Controller Backpanel”on page 98

Controller Fan Go to “Replacing a Failed Controller Fan” onpage 106

Power Supply Go to “Replacing a Failed Power Supply” onpage 122

Power Supply Fan Go to “Replacing a Failed Power Supply Fan” onpage 109

Replace FRUs in the DeviceDrawer Drive Go to “Replace a Failed Drive” on page 160

ESM board Go to “Replace a Failed ESM FRU” on page 170

Fan Go to “Replace a Failed Fan” on page 188

Power Supply Go to “Replace a Failed Power Supply” onpage 183

Replace FRUs in the FibreChannel Hub

Refer to Fibre Channel Storage Hub, Installation, Service, and User’s Guide, IBM2103 Model H07, SC26-7289.


Table 2. 2102 Fibre Channel RAID Storage Server Start Table B (continued)



Power On/Off SubsystemComponents

Note: Subsystem components must be powered up in the correct sequence toensure proper operation.Power Up Sequence:

1. rack (ensure that power for attached subsystem components is off)

2. hub

3. device drawers

4. controller module

5. host (wait until all drives have spun up to speed)

Power Off Sequence:

1. host (if applicable)

2. controller module

3. device drawers

4. hub

5. rack

Component Power On/Off Procedures:

rack Rack power is active when each PowerDistribution Unit (PDU) power cord is plugged in.A green light on the PDU indicates that power isactive to that PDU. Each PDU should bepowered on before continuing.

hub Hub power is active when the hub power cord isplugged in.

Device Drawer Wait at least 30 seconds after powering off adevice drawer before turning power back on. Turnon both power switches on the back of thedrawer. An LED on the back of the ESM boardindicates that power is active. Refer to “Turn Onthe Power” on page 153 and “Turn Off the Power”on page 154 for details.

Controller Module Turn on/off both power switches on the back ofthe module. An LED on the front panel indicatesthat power is active. Refer to “Turning On thePower” on page 72 and “Turning Off the Power”on page 74.

host See your host system documentation


Table 2. 2102 Fibre Channel RAID Storage Server Start Table B (continued)



The host cannot communicatewith one or both of thecontrollers, but there is no LEDindication of any subsystemfaults.

1. Go to “Identifying Interface Problems” on page 87 and follow the procedure forthe debugging of interface problems. If this fails to solve the problem, then go toStep 2.

2. Connect a service terminal to the top serial port on the back of the controllermodule and start RAID Manager for DOS (DRM). See “Chapter 16. RAIDManager for DOS” on page 205 for information on setting up and starting DRM.

3. Using DRM, run the Array Monitor utility to check the current status of arraycomponents and verify the communication paths within the array subsystem.Follow the procedure in “Verifying the Installation” on page 212.

v If the Array Monitor indicates a component failure within the array, then replacethe failed component.

v If the Array Monitor runs without indicating a failure (that is, it displays themessage ″Waiting for Next Polling Period″), then go to Step 4.

4. Using DRM, run the Array Configuration Editor (ACE) to verify thecommunications between the controllers and the devices and check the status ofthe devices.

a. If ACE indicates that the controller is not communicating over a specific drivechannel (that is, the Drive Window in ACE shows no devices on channel 6,but there is a SCSI cable connected to channel 6 on the back of thecontroller module), then replace the SCSI cable connected to that channel.

b. If ACE indicates that the controller is not communicating with a specific driveor indicates a failure on a specific drive, then replace the defective drive.

c. If ACE indicates a problem with LUN 0 or LUN 0 is not optimal, then you mustfix the problem with LUN 0 in order to enable communication with the host. Ifthe problem cannot be fixed by replacing hardware, you may need to deleteand recreate LUN 0. If you do this, all data on LUN 0 will be lost. Make surethe customer is aware of your actions and call your next level of support forassistance.Note: One possible case of an off-line LUN 0 can occur when a drive drawercontaining LUN 0 configuration information is added to an existing subsystem.In this case, the subsystem has conflicting information about the LUN 0configuration and you must remove and rebuild the LUN.

d. If ACE does not indicate any failures or communications problems, then go toStep 5.

5. Repeat steps 2 through 5 using the bottom serial port on the back of thecontroller module.

6. There is a problem with the Fibre Channel host adapter or in the fibre channelpath between the host and the subsystem. Perform the following steps:

a. Recheck the fibre channel cables between the host and the controller andreplace if necessary.

b. If there is a hub in the fibre channel path, verify that there are no failures inthe hub. See Fibre Channel Storage Hub, Installation, Service, and User’sGuide, IBM 2103 Model H07, SC26-7289 for details.

c. Verify that the host fibre channel adapter is configured properly.

d. Verify that the host fibre channel adapter is at the correct firmware level.

e. Verify that the host fibre channel adapter is working properly and replace ifnecessary. If the subsystem is attached to a system running AIX, rundiagnostics from the host on the fibre channel adapter to check for problems.For information on running diagnostics on the adapter refer to DiagnosticInformation for Multiple Bus Systems, SA38-0509.


Start Table CTable 3. 2102 Fibre Channel RAID Storage Server Start Table C



Use Fibre Channel StorageManager for AIX

See Fibre Channel Storage Manager, Installation and User’s Guide for the AIXOperating System, SC26-7290.

Download Controller Firmware The controller firmware download function is provided by the host storagemanagement software:

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then upgrade the controller firmware using the Maintenance and TuningApplication. Refer to Fibre Channel Storage Manager and StorWatch FibreChannel RAID Specialist, User’s Guide, SC26-7285.

v If the subsystem is attached to an AIX host system, then upgrade the controllerfirmware using the AIX Diagnostic Service Aids (″Fibre Channel RAID Tasks″).Refer to the Fibre Channel Storage Manager, Installation and User’s Guide for theAIX Operating System, SC26-7290.

Update Controller NVSRAM The update controller NVSRAM function is provided by the host storage managementsoftware:

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then update the controller NVSRAM using the Maintenance and Tuningapplication. Refer to Fibre Channel Storage Manager and StorWatch FibreChannel RAID Specialist, User’s Guide, SC26-7285.

v If the subsystem is attached to an AIX host system, then upgrade the controllerfirmware using the AIX Diagnostic Service Aids (″Fibre Channel RAID Tasks″).Refer to Fibre Channel Storage Manager, Installation and User’s Guide for the AIXOperating System, SC26-7290.

Download Drive Firmware The drive firmware download function is provided by a software utility that runs onthe host system:

v For Windows NT host systems, refer to “Downloading Drive Microcode fromWindows NT using DriveDload” on page 239.

v For SUN Solaris or HP-UX host systems, refer to “Downloading Drive Microcodefrom HP-UX or SUN Solaris Using drvDLoad” on page 244.

v For AIX host systems, use the AIX Diagnostic Service Aids (″Fibre Channel RAIDTasks″). Refer to Fibre Channel Storage Manager, Installation and User’s Guidefor the AIX Operating System, SC26-7290.

Configure the Subsystem The subsystem configuration functions are provided by the Fibre Channel StorageManager software running on the host. Refer to the software documentation for yoursystem for the appropriate procedure.


Table 3. 2102 Fibre Channel RAID Storage Server Start Table C (continued)



Check the Status of SubsystemComponents

Subsystem component status can be checked from the host using the statusfunctions provided by the host storage management software. Component statusmay also be checked using a service tool connected to the controller module via theRS232 port.

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then run the Status application from the host system. Refer to FibreChannel Storage Manager and StorWatch Fibre Channel RAID Specialist, User’sGuide, SC26-7285.

v If the subsystem is attached to an AIX host system, then follow the procedures inthe Fibre Channel Storage Manager, Installation and User’s Guide for the AIXOperating System, SC26-7290 for checking the status of subsystem components.

v To check the subsystem component status from the service tool, go to “Using theArray Monitor” on page 223.

Install the Subsystem orSubsystem Components subsystem Go to “Chapter 2. Installation And Removal

Guide” on page 35.

hub Go to ″Rack Installation″ in Fibre ChannelStorage Hub, Installation, Service, and User’sGuide, IBM 2103 Model H07, SC26-7289

drive modules Go to “Installing the Drive Module” on page 49.

controller module Go to “Installing the Controller Module” onpage 45.

Use RAID Manager for DOS(DRM)

Go to “Chapter 16. RAID Manager for DOS” on page 205

Decipher LEDshub Go to ″Port Status LEDs″ in Fibre Channel

Storage Hub, Installation, Service, and User’sGuide, IBM 2103 Model H07, SC26-7289

device drawer and drives Go to “Check the Overall Hardware Status” onpage 156.

controller module Go to “Using the Status LEDs” on page 75.


Start Table DTable 4. 2102 Fibre Channel RAID Storage Server Start Table D



Check Cables Refer to the following sections for cable locations and debug procedures:

hub

v For an example of proper GBIC and fiber optic cable installation, see ″Installingthe GBIC″ in Fibre Channel Storage Hub, Installation, Service, and User’s Guide,IBM 2103 Model H07, SC26-7289.

v For an example of a host bus adapter with a GBIC attached, see ″Attaching aGBIC to Initiators and Targets″ in Fibre Channel Storage Hub, Installation, Service,and User’s Guide, IBM 2103 Model H07, SC26-7289.

v For GBIC and cable debug procedures, see ″Troubleshooting″ in Fibre ChannelStorage Hub, Installation, Service, and User’s Guide, IBM 2103 Model H07,SC26-7289.

Device Drawer

v For SCSI connector locations on the ESM board, see “Environmental ServicesMonitor Board” on page 146.

v For SCSI cable installation and routing information, see “LVD-SCSI Drive CableRouting Examples” on page 59.

v For SCSI cable technical information, see “Interface Connections and Cables” onpage 193.

v For SCSI cable troubleshooting procedures, see “Hints for TroubleshootingInterface Problems” on page 169.

Controller Module

v For controller interface connector locations, see “Interface Connectors and Cables”on page 41

v For cable troubleshooting hints, see “Controller and Interface Problems” onpage 133.

Identify SubsystemComponents v If the subsystem is attached to a Windows NT, SUN, or HP-UX host system

running the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then you can identify disk drives, drive groups and logical units using theConfiguration application. Refer to Fibre Channel Storage Manager and StorWatchFibre Channel RAID Specialist, User’s Guide, SC26-7285.

v If the subsystem is attached to an AIX host system, then follow the procedures inthe ″Problem Determination and Recovery″ chapter of Fibre Channel StorageManager, Installation and User’s Guide for the AIX Operating System, SC26-7290for identifying subsystem components.

v The disk drives that comprise a particular Logical Unit (LUN) can also be identifiedby using a service tool that is connected to the controller module via the RS232port. See “Identifying Drives and Logical Units” on page 222 for details.


Table 4. 2102 Fibre Channel RAID Storage Server Start Table D (continued)



View Message or Error Logs Message and error logs are maintained on the host system. Refer to the host systemdocumentation for information on accessing and analyzing the system logs.

v The Fibre Channel Storage Manager software for Windows NT, Sun Solaris andHP-UX, and the StorWatch Fibre Channel RAID Specialist software for WindowsNT or Windows 95 also maintains a separate message log that can be viewedfrom within the status application. Refer to Fibre Channel Storage Manager andStorWatch Fibre Channel RAID Specialist, User’s Guide, SC26-7285.

v On AIX host systems, the error and message logging is integrated with operatingsystem error log. The AIX operating system contain functions for analyzing thesystem log and indicating the appropriate recovery actions. Refer to Fibre ChannelStorage Manager, Installation and User’s Guide for the AIX Operating System,SC26-7290 and Diagnostic Information for Multiple Bus Systems, SA38-0509 formore information.

Perform a Health Check v If the subsystem is attached to a Windows NT, SUN, or HP-UX system running theFibre Channel Storage Manager software or a Windows NT or Windows 95 systemrunning the StorWatch Fibre Channel RAID Specialist software, then you canperform an immediate health check by using the Recovery application. There isalso a background array monitor that checks the subsystem component status atintervals defined by the operator. Refer to Fibre Channel Storage Manager andStorWatch Fibre Channel RAID Specialist, User’s Guide, SC26-7285 for moreinformation.

v On subsystems attached to an AIX host, the passive controller health checkprovides monitoring capability for testing components that are not actively in use.The health check frequency can be set from in the Disk Array Routerconfiguration. Refer to Fibre Channel Storage Manager, Installation and User’sGuide for the AIX Operating System, SC26-7290 for more information.

Perform a Parity Check/Repair The Parity Check/Repair function scans a logical unit, checks the array parity foreach block in the LUN and repairs any parity errors found.

Note: If array parity errors result from corrupted data, the data is not repaired. Onlythe array parity is changed to be consistent with the data.

The parity Check/Repair function can be initiated from the host using the hoststorage management software.

v If the subsystem is attached to a Windows NT, SUN, or HP-UX system running theFibre Channel Storage Manager software or a Windows NT or Windows 95 systemrunning the StorWatch Fibre Channel RAID Specialist software, then you can run aparity check/repair from the Recovery application. Refer to the Fibre ChannelStorage Manager and StorWatch Fibre Channel RAID Specialist, User’s Guide,SC26-7285.

v If the subsystem is attached to an AIX host system, then you can run the paritycheck/repair from the Disk Array menu. Refer to Fibre Channel Storage Manager,Installation and User’s Guide for the AIX Operating System, SC26-7290 for moreinformation.

Certify a LUN or a SparePhysical Disk

The Certify function checks a LUN or disk for defective sectors. This service is onlyavailable from the Diagnostic Service Aids menu on AIX host systems. Refer to FibreChannel Storage Manager, Installation and User’s Guide for the AIX OperatingSystem, SC26-7290 for more information.

Format a Failed Physical Disk If the subsystem is attached to a system running AIX, use Format service aidprovided by AIX diagnostics. For details, refer to Fibre Channel Storage Manager,Installation and User’s Guide for the AIX Operating System, SC26-7290.


Table 4. 2102 Fibre Channel RAID Storage Server Start Table D (continued)



Revive a dead LUN v If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then refer to the Fibre Channel Storage Manager and StorWatch FibreChannel RAID Specialist, User’s Guide, SC26-7285 for information on revivingLUNs.

v If the subsystem is attached to an AIX host system, then follow the procedures inthe ″Problem Determination and Recovery″ chapter of Fibre Channel StorageManager, Installation and User’s Guide for the AIX Operating System, SC26-7290for reviving dead LUNs.

AIX Error Codes (SRNs)

Error Codes are generated for the subsystem by the system error-log analysis anddiagnostics. Error codes help you identify the cause of the problem, the failing fieldreplaceable units (FRUs), and the service actions that might be needed to solve theproblem.

The Error Code Table

The table in this section lists the Error Codes and describes the actions you shouldtake. The table columns are:

EC The Error Code

FRU The FRU or FRUs that might be causing theproblem

Description A description of the problem and the actions to take

Using the Error Code Table

Important: Do not start problem determination from the Error Code table; alwaysbegin with the 2102 Fibre Channel RAID Storage Server Start Tablesthat start on page 4.

1. Locate the Error Code in the table. If you cannot find the Error Code, then thereis a problem with the diagnostics, the microcode, or the documentation. Callyour next level of support for assistance.

2. Read carefully the ″Action″ you are instructed to perform. Do not exchangeFRUs until you have read through all procedures referenced in the ″Action″field. Then replace FRUs in the order they are listed in the FRU column of theError Code table.

Note: If the Error Code has been generated by diagnostics, and you areinstructed to use the disk array manager, you must end the diagnostics.The disk array manager cannot run while the subsystem is in diagnosticmode.

3. For information about the disk array manager, see the Fibre Channel StorageManager, Installation and User’s Guide for the AIX Operating System,SC26-7290.


4. Normally, you will exchange only one FRU at a time, starting from the top of theFRU list for that Error Code. Always follow the instructions given in this manualwhen exchanging FRUs; a reference is given with each Error Code entry.

The first three digits of the error code indicate the type of failure or the FRU thatmost likely failed, as follows:

444 Controller with 256 MB cache

555 Fan

641 DDRS-39130D 9GB Disk Drive

658 Controller with 128 MB cache

666 Power Supply

670 DGHS18D 18 GB Disk Drive

671 DGHS09D 9 GB Disk Drive

677 Fibre Channel Adapter

679 DDRS-34560D 4.5 GB Disk Drive

777 Cache Battery

888 AC Line

999 Over Temperature Indicator

Table 5. AIX Error Codes

EC FRU Description

444101v SCSI cables

v Controller Card - see “Replacing aFailed Controller” on page 93.

v ESM board - see “Replace a FailedESM FRU” on page 170.

v Controller backpanel - see “Replacing aFailed Controller Backpanel” onpage 98.

A SCSI problem was detected.

Action: Read the procedures in “Hints for TroubleshootingInterface Problems” on page 169 for debugging SCSI interfaceproblems. If the problem is not resolved, then replace FRUs inthe order listed here.

444102v Controller Card - see “Replacing a

Failed Controller” on page 93.


One of two array controller cards failed or powered down.

Action: Read the procedure in “Troubleshooting ControllerProblems” on page 92 and, if necessary, replace the FRUs asindicated.



v Fibre Channel Adapter


The device failed to open in Diagnostic mode.

Action: Follow the procedures in “Troubleshooting ControllerProblems” on page 92 and replace FRUs as indicated.





The controller configuration failed.



Table 5. AIX Error Codes (continued)

EC FRU Description

444105v SCSI cables


v Device Drawer Midplane/Chassis - see“Replace a Failed MidPlane” onpage 173.



v Device Drawer Power Supplies - see“Replace a Failed Power Supply” onpage 183.

Cannot access physical disks.


Note: This error is typically caused by a SCSI interfaceproblem, but can also occur if there is no power to a devicedrawer. This is why the device drawer power supplies arelisted in the FRUs at left.

444106v SCSI cables

v Disk Drive - see “Replace a FailedDrive” on page 160.

v Controller Card - see “Replacing aFailed Controller” on page 93



A physical disk failed to respond.

Action: Read the procedure in “Hints for TroubleshootingInterface Problems” on page 88 and “Hints for TroubleshootingInterface Problems” on page 169 for debugging interfaceproblems and exchange SCSI cables if necessary. If theproblem persists, then refer to the procedures in “Maintainingthe Drives” on page 160 and “Identify Other Drive-RelatedProblems” on page 164 for debugging drives and drive relatedproblems, and replace a failed disk drive if instructed. If theproblem persists, then refer to the procedures in“Troubleshooting Controller Problems” on page 92 fordebugging controller problems and replace FRUs asinstructed.

444107v SCSI cables



The controller failed to become active due to an inter-controllercommunications failure.

Action: Read the procedure in “Hints for TroubleshootingInterface Problems” on page 88 and “Hints for TroubleshootingInterface Problems” on page 169 for debugging interfaceproblems and exchange SCSI cables if necessary. If theproblem persists, then refer to the procedures in“Troubleshooting Controller Problems” on page 92 fordebugging controller problems and replace FRUs asinstructed.

444108 Disk Drive - see “Replace a Failed Drive”on page 160.

The controller failed to become active due to a non-supporteddrive.

Action: Use the system problem determination procedureswith error log analysis to identify the failing disk drive. Thenexchange the FRU for a new FRU.



EC FRU Description

444121 Any subsystem component Error Log Analysis indicates a subsystem failure.

Action: If the ELA identifies the source of the problem, thenreplace the FRU(s) indicated. If the ELA does not identify thesource of the problem, then check the subsystem LEDs (see“Using the Status LEDs” on page 75 and “Check the OverallHardware Status” on page 156) and go to the START table.

If the LEDs do not indicate a problem, then run AdvancedDiagnostics in System Verification mode on the controller thatreported the failure and use the SRN generated to debug thefailure.


Failed Controller” on page 93


Error Log Analysis indicates an active controller failure.

Action: Exchange the FRU for a new FRU.




Error Log Analysis indicates a passive controller failure.


444124v SCSI cables



Error Log Analysis indicates an inter-controller communicationsfailure.


444125v Fibre Channel Adapter



Error Log Analysis indicates that the configuration of thecontroller has changed.

Action: Run Advanced Diagnostics in System VerificationMode through the adapter and array controller for which theproblem was reported, to confirm the error. Exchange theFRUs for new FRUs.




Error Log Analysis indicates a controller switch failure.

Action: Run Advanced Diagnostics in System VerificationMode through the adapter and array controller for which theproblem was reported, to confirm the error. Exchange theFRUs for new FRUs.



EC FRU Description

555202 The list of possible failing FRUs dependson the enclosure identified in thediagnostic failure information (See“Location Codes Displayed ByDiagnostics” on page 31):

Controller Module (EID E0):

v Controller Fan - see “Replacing aFailed Controller Fan” on page 106.

v Controller Power Supply Fan - see“Replacing a Failed Power Supply Fan”on page 109.

v Controller Backpanel - see “Replacinga Failed Controller Backpanel” onpage 98.

Drive Drawer (EID E2 – E6):

v Device Drawer Fan - see “Replace aFailed Fan” on page 188.


Critical fan fault. Two or more fan assemblies have failed.

Action:

v For Controller Module fan failures, read the procedure in“Servicing the Cooling System” on page 101 and replaceFRUs as instructed.

v For Drive Drawer fan failures, read the procedure in“Maintaining the Cooling Fans” on page 187 and replaceFRUs as instructed.






Drive Drawer (EID E2 – E6):



Enclosure status reports a non-critical fan failure.

Action:

v For Controller Module fan failures, read the procedure in“Servicing the Cooling System” on page 101 and replaceFRUs as instructed.

v For Drive Drawer fan failures, read the procedure in“Maintaining the Cooling Fans” on page 187 and replaceFRUs as instructed.


A drive failed. Test Unit Ready failure.



The disk drive failed due to an unknown cause.




EC FRU Description


An incorrect disk drive module was removed/replaced.

Action: If you replaced the wrong drive, but the logical unit isnot being written, then replacing the drive you removedimmediately should restore the logical unit and prevent dataloss. In other instances, you may be able to restore the arraywithout losing any data by ″reviving″ the drive. Call your nextlevel of support for direction.


Read failure.



Incorrect sector size.

Action: Format the drive using the AIX Disk Array Manager. Ifthis fails to fix the problem, then exchange the FRU for a newFRU.


The drive does not respond or a defined Global Hot Sparedrive is missing.



Incorrect Disk capacity. The disk drive might belong to adifferent logical unit.

Action: Format the drive using the Fibre Channel RAIDManager. If this fails to fix the problem, then exchange theFRU for a new FRU.


The drive failed to format or reconstruct.



Write failure.



The drive was failed by the user via a Mode Select.

Action: If the drive was failed for the purpose of replacing thedrive, then exchange the failed drive for a new FRU. If youwish to revive the same drive and bring it back into the array,then use the Fibre Channel RAID Manager to make the driveoperational.


A drive failed. Controller storage failure.


641202 Disk Drive(s) - see “Replace a FailedDrive” on page 160.

Enclosure status reports a critical disk failure.



Enclosure status reports a non-critical disk failure.



Error Log analysis indicates predictive failure analysis.




EC FRU Description


Error Log Analysis indicates that the physical disk does notsupport dual-active configuration.



Error Log Analysis indicates a physical disk failure.


658101v SCSI cables




A SCSI problem was detected.





One of two array controller cards failed or powered down.

Action: Read the procedure in “Troubleshooting ControllerProblems” on page 92 and, if necessary, replace the FRUs asindicated.





The device failed to open in Diagnostic mode.






The controller configuration failed.


658105v SCSI cables





v Device Drawer Power Supplies - see“Replace a Failed Power Supply” onpage 183.

Cannot access physical disks.


Note: This error is typically caused by a SCSI interfaceproblem, but can also occur if there is no power to a devicedrawer. This is why the device drawer power supplies arelisted in the FRUs at left.



EC FRU Description

658106v Disk Drive - see “Replace a Failed

Drive” on page 160.

v SCSI cables




A physical disk failed to respond.

Action: Read the procedure in “Hints for TroubleshootingInterface Problems” on page 88 and “Hints for TroubleshootingInterface Problems” on page 169 for debugging interfaceproblems and exchange SCSI cables if necessary. If theproblem persists, then refer to the procedures in “Maintainingthe Drives” on page 160 and “Identify Other Drive-RelatedProblems” on page 164 for debugging drives and drive relatedproblems, and replace a failed disk drive if instructed. If theproblem persists, then refer to the procedures in“Troubleshooting Controller Problems” on page 92 fordebugging controller problems and replace FRUs asinstructed.

658107v SCSI cables



The controller failed to become active due to an inter-controllercommunications failure.



The controller failed to become active due to a non-supporteddrive.

Action: Use the system problem determination procedureswith error log analysis to identify the failing disk drive. Thenexchange the FRU for a new FRU.

658121 Any subsystem component Error Log Analysis indicates a subsystem failure.

Action: If the ELA identifies the source of the problem, thenreplace the FRU(s) indicated. If the ELA does not identify thesource of the problem, then check the subsystem LEDs (see“Using the Status LEDs” on page 75 and “Check the OverallHardware Status” on page 156) and go to the START table.

If the LEDs do not indicate a problem, then run AdvancedDiagnostics in System Verification mode on the controller thatreported the failure and use the SRN generated to debug thefailure.




Error Log Analysis indicates an active controller failure.




EC FRU Description




Error Log Analysis indicates a passive controller failure.

Important: Diagnostics may take a long time (up to 40minutes) if interface problems exist.

Action:

1. If you have not already done so, run the AdvancedDiagnostics in System Verification mode from thediagnostics interface (type diag from the commandprompt).

If the controller does not return to the On-line status, thenthe problem is at the connection or RAID controller. Go toStep 2 to check the connection. If the controller returns tothe On-line status, then return to normal operation (seeMAP 0410 in Diagnostic Information for Multiple BusSystems, SA38-0509).

2. Check both ends of the connections of external cables andhubs for bent pins, loose connections, or visible damage. Ifthere is a problem with the connection, go to Step 3. Ifthese components are OK, you probably have a defectiveRAID Controller. Go to Step 4.

3. Fix the connection problem (for example, reconnect orreplace cable), then rerun the Advanced Diagnostics inSystem Verification mode.

If the controller does not return to the On-line status, thenyou probably have a defective RAID controller. Go to step4 to replace the RAID controller. If the controller returns tothe On-line status, then return to normal operation (seeMAP 0410 in Diagnostic Information for Multiple BusSystems, SA38-0509).

4. Replace the controller using the procedure in “Replacing aFailed Controller” on page 93.

5. Run the Advanced Diagnostics in System Verification modefrom the diagnostics interface.

If the controller does not return to the On-line status, thenyou may have a defective controller backpanel. Go to Step6 to replace the backpanel. If the controller returns to theOn-line status, then return to normal operation (see MAP0410 in Diagnostic Information for Multiple Bus Systems,SA38-0509).

6. Replace the controller backpanel using the procedure in“Replacing a Failed Controller Backpanel” on page 98.

7. Run the Advanced Diagnostics in System Verification modefrom the diagnostics interface.

If the controller does not return to the On-line status, thenyou may have a defective adapter. If the controller returnsto the On-line status, then return to normal operation (seeMAP 0410 in Diagnostic Information for Multiple BusSystems, SA38-0509).

Note: If you replaced the controller and the file systems orlogical units or both do not respond, you may need to rebootyour system.



EC FRU Description

658124 v SCSI cables



Error Log Analysis indicates an inter-controller communicationsfailure.





Error Log Analysis indicates that the configuration of thecontroller has changed.

Action: Run the Advanced Diagnostics in System Verificationmode through the adapter and array controller for which theproblem was reported, to confirm the error. Exchange theFRUs for new FRUs.




Error Log Analysis indicates a controller switch failure.

Action: Run the Advanced Diagnostics in System VerificationMode through the adapter and array controller for which theproblem was reported, to confirm the error. Exchange theFRUs for new FRUs.



v Controller Power Supply - see “Replacea Failed Power Supply” on page 183.

Drive Drawer (EID E2 - E6):

v Device Drawer Power Supply - see“Replace a Failed Power Supply” onpage 183.

Enclosure status reports a critical power supply failure.

Action:

v For Controller Module power system failures, read theprocedure “Servicing the Power System” on page 111 andreplace FRUs as instructed.

v For Drive Drawer power system failures, read the procedurein “Maintaining the Power System” on page 180 and replaceFRUs as instructed.



EC FRU Description








Enclosure status reports a non-critical power supply failure.

Action:













Read failure.













EC FRU Description





Write failure.






























An incorrect disk drive module was removed or replaced.

Action: If you replaced the wrong drive, but the logical unit isnot being written, then replacing the drive you removedimmediately should restore the logical unit and prevent dataloss. In other instances, you maybe able to restore the arraywithout losing any data by ″reviving″ the drive. Call your nextlevel of support for direction.


Read failure.







EC FRU Description











Write failure.


























The Fibre Channel adapter configuration failed.

Action: Replace the Fibre Channel Adapter card indicated. Ifthe problem persists, follow the procedures in “TroubleshootingController Problems” on page 92 and replace FRUs asindicated.






EC FRU Description








Read failure.




Action: Format the drive using the Diagnostic Format ServiceAid. If this fails to fix the problem, then exchange the FRU fora new FRU.






Action: Format the drive using the Diagnostic Format ServiceAid. If this fails to fix the problem, then exchange the FRU fora new FRU.





Write failure.



















EC FRU Description







777110v Cache Battery - see “Replacing the

Battery FRU” on page 116

v Controller Power Supply - see“Replacing a Failed Power Supply” onpage 122

v Cache Battery Harness - see“Replacing the Battery Harness” onpage 125

The array controller indicates a cache battery failure.

Action: Refer to the procedures in “Troubleshooting BatteryProblems” on page 114 for debugging battery problems andreplace FRUs as instructed.





The alternate array controller indicates a cache battery failure.






Error Log Analysis indicates an array controller cache battery
















EC FRU Description








Enclosure status reports that the AC line voltage has failedand the subsystem is operating on UPS.

Action:










v Device Drawer ESM module - see“Replace a Failed ESM FRU” onpage 170.


Enclosure status reports the subsystem is operating at atemperature above the safe operating temperature.

Action:

v For Controller Module fan failures, read the procedure“Determining Which Fan Failed” on page 102 and replaceFRUs as instructed. If the problem persists, replace thecontroller backpanel.

v For Drive Drawer fan failures, replace the Device DrawerFan. If the problem persists, replace the ESM. If theproblem still persists, replace the device drawermidplane/chassis.



EC FRU Description

999203 The list of possible failing FRUs dependson the enclosure identified in thediagnostic failure information (See“Location Codes Displayed ByDiagnostics”):







v Device Drawer ESM module - see“Replace a Failed ESM FRU” onpage 170.


Enclosure status reports that the subsystem is operating athigher than normal temperature.

Action:

v For Controller Module fan failures, read the procedure“Determining Which Fan Failed” on page 102 and replaceFRUs as instructed. If the problem persists, replace thecontroller backpanel.

v For Drive Drawer fan failures, replace the Device DrawerFan. If the problem persists, replace the ESM. If theproblem still persists, replace the device drawermidplane/chassis.

Location Codes Displayed By Diagnostics

When the AIX diagnostics detect a failure in the 2102 Fibre Channel RAIDsubsystem, the failure information includes a location code used to physicallyidentify the failing component within the subsystem. The following describes how tointerpret the reported location codes:

v Translating location codes for a disk drive failure:

Disk drive failures will be reported in the following format:653153: Drive failed by user via Mode Select.Refer to the 2102 Model F10 Service Guide for more information.100% 17.357GB CH5 ID8 D0 Disk module

Location code CH5 ID8 D0 indicates that the failing disk drive is on channel 5,SCSI ID 8 and is assigned to dac0.

v Translating location codes for other subsystem component failures (otherthan disk drives):

Subsystem component failures, other than disk drives, will be reported in thefollowing format:

555203: Enclosure status reports a non-critical fan failure.Refer to the 2102 Model F10 Service Guide for more information.100% E6 D0 Fan module

Location code E6 D0 means the fan is in the enclosure with EID=6 and assignedto dac0.


EID Enclosure

E0 Controller

E2 Enclosure attached to SCSI channel 1







Part 2. Installation and Removal


Chapter 2. Installation And Removal Guide

Preparatory Tasks

This section specifies the preparations you should have completed before beginningthe installation and explains the overall installation process. Read everything inthis section before starting the installation procedure. The instructions in thisbook are based on the following assumptions:

v The applicable host adapter has been installed and configured in the hostmachine.

v The applicable RAID storage management software has been installed on thehost machine, aided by the following publications:

– Fibre Channel Storage Manager, Installation Guide for Microsoft Windows NT,SC26-7283

– Fibre Channel Storage Manager, Installation Guide for Hewlett PackardHP-UX Operating System, SC26-7287

– Fibre Channel Storage Manager, Installation Guide for Sun Solaris OperatingSystem, SC26-7286

– Fibre Channel Storage Manager, Installation and User’s Guide for the AIXOperating System, SC26-7290

– StorWatch Fibre Channel RAID Specialist, Installation Guide for MicrosoftWindows NT and Windows 95, SC26-7284

v You have read all the readme files on the software installation, CDs, and anyerrata sheets shipped with the subsystem for updated information.

v Fibre Channel interface cables are attached to the appropriate hosts and areready for final connection to the controller module (See “Fibre Channel HostCable Requirements” on page 42).

v The installation site meets all area, environmental, power, and site requirements(Refer to “Preparing the Site” on page 36).

v You have moved the cabinet to its permanent operation location and prepared itfor final installation (See “Preparing the Rackmount Cabinet” on page 43).

v A power outlet is available near the final installation site to power a serviceterminal.

Tools and Equipment You May Need

To complete the installation procedure, you will need some or all of the following:

v The appropriate power cords

v Screwdrivers and wrenches (various sizes)

v Antistatic protection (such as a grounding wrist strap)

v Interface cables and tie wraps

v Mounting hardware for any rack components that are not yet installed in the rack

v Table or cart (optional)

About the Installation Procedure

The step-by-step procedures in this chapter will guide you through the entireinstallation process. These procedures include:


v Preparing the site

v Preparing the cabinet

v Preparing the drive modules

v Preparing the controller module

v Completing the installation

You should perform these tasks in the order given, beginning with “Preparing theSite”.

Preparing the Site

This section lists the space, environmental, and power requirements for the 2102subsystem. For information on interface cables and connections, refer to “FibreChannel Host Cable Requirements” on page 42 and “LVD-SCSI Drive CableRequirements” on page 42.

Floor Space

The floor area at the installation site must provide:

v Enough stability to support the weight of the controller module, drive modulesand associated equipment. (Table 6 and Table 7 on page 37).

v Sufficient space to install and service the controller module, drive modules andassociated equipment. Allow a 36 inch wide service area in front and back of thesubsystem components (see Table 8 on page 37 and Figure 1 on page 37 forcontroller module dimensions; Table 9 on page 37 and Figure 2 on page 38 fordrive module dimensions).

Weight

The rack’s total weight depends on the number of components installed in the rack.Table 6 and Table 7 on page 37 respectively list the overall weight of the controllermodule and the drive module (unit and shipping), plus the weight for individualcomponents. The maximum weight equals a controller module or a drive modulefully populated with the heaviest FRUs. Empty weight equals a controller module ordrive module with all FRUs removed.

Table 6. Controller Module Weight

WeightCriteria

Controller Module Weight Individual Component Weight

Maximum Empty Controller Battery ControllerFan

Power SupplyFan

PowerSupply

Unit 34.5 kg (76.0lb)

14.3 kg(31.6 lb)

3.0 kg (6.6 lb) 9.7 kg(21.4 lb)

0.9 kg (1.9 lb) 0.7 kg (1.5 lb) 1.5 kg (3.3lb)

Shipping 48.5 kg(107.0 lb)

28.4 kg(62.6 lb)


Table 7. Drive Module Weight

WeightCriteria

Drive Module Weight Individual Component Weight

Maximum Empty 18 GBDrive FRU

9 GB DriveFRU

4.5 GBDrive FRU

ESM FRU PowerSupplyFRU

Fan FRU

Unit 40.13 kg(88.3 lb)

10.3 kg(22.6 lb)

1.93 kg(4.23 lb)

1.63 kg(3.57 lb)

1.63 kg(3.57 lb)

2.77 kg(6.1 lb)

2.9 kg (6.4lb)

.98 kg(2.16 lb)

Shipping 58.53 kg(128.8 lb)

28.7 kg(63.1 lb)

Dimensions

Table 8 and Table 9 lists the controller module and drive module dimensions, withand without the front cover, in and out of a shipping carton. Figure 1 and Figure 2on page 38 show dimensions for the controller and drive modules, respectively.

Table 8. Controller Module Dimensions Table

Criteria Height Width Depth

With Front Panel 17.4 cm (6.8 in.) 48.2 cm (19 in.) 63.5 cm (25 in.)

No Front Panel 17.4 cm (6.8 in.) 44.5 cm (17.5 in.) 60.6 cm (23.8 in.)

Packaged for Shipping 44.5 cm (17.5 in.) 62.2 cm (24.5 in.) 78.7 cm (31 in.)

Table 9. Drive Module Dimensions Table


With Front Panel 13.3 cm (5.2 in.) 48.2 cm (19.0 in.) 57.2 cm (22.5 in.)

Figure 1. Controller Module Dimensions

Chapter 2. Installation And Removal Guide 37

Table 9. Drive Module Dimensions Table (continued)


No Front Panel 12.9 cm (5.1 in.) 44.7 cm (17.6 in.) 55.9 cm (22.0 in.)

Packaged for Shipping 38.1 cm (15.0 in.) 61.4 cm (24.0 in.) 83.2 cm (32.7 in.)

Heating and Air Conditioning

Table 10 lists the temperature, humidity, and air flow requirements for the controllerand drive modules.

Table 10. Environmental Requirements

Element Unit of Measure Requirement

Air Flow Air flows from front to back

Altitude Below Sea LevelAbove Sea Level

Operating Range 30.5 m (100 ft.)3,000 m (9,840 ft.)

Storage Range 30.5 m (100 ft.)3,000 m (9,840 ft.)

Transit Range 30.5 m (100 ft.)12,000 m (40,000 ft.)

Temperature Optimum¹ 22° C (72° F)

Operating Range¹ 10° C to 40° C (50° F to 104° F)

Storage Range -10° C to 50° C (14° F to 122° F)

Transit Range -40° C to 60° C (-40° F to 140° F)

Temperature Change (maximumallowed)

Operating Range 10° C (18° F) per hour

Storage Range 15° C (27° F) per hour

Transit Range 20° C (36° F) per hour

Figure 2. Dimensions of Drive Module


Table 10. Environmental Requirements (continued)

Element Unit of Measure Requirement

Relative Humidity (nocondensation)

Operating Range 20% to 80%

Storage Range 10% to 90%

Transit Range 5% to 95%

Maximum Dew Point 26° C (79° F)

Maximum Humidity Gradient 10% per hour

¹ If you plan to operate the controller module at altitudes between 1000 m and 3000 m (3280 ft. and 9850 ft.), youmust lower the environmental temperature 1.7° C (3.3° F) for every 1000 m (3280 ft.) above sea level.

Electrical

Table 11 and Table 12 list the electrical power requirements for the controller anddrive modules.

Table 11. Controller Module Power Requirements

Item Unit of Measure Requirement

Circuit Breaker 3.0 A (slow-blow fuse per power supply)

Controller Module ACPower

Nominal Voltage 90 to 264 v AC

Frequency 50/60 Hz

Idle Current 1.0¹

Maximum Operating Current 1.0¹

Maximum Surge Current 2.0¹

¹ Typical current at 240 v AC, 60 Hz (assumes 0.70 power efficiency, 0.99 power factor).

Table 12. Drive Module Power Requirements

Item Unit of Measure Requirements

USA and Canada International

AC Power Nominal Voltage 100 v AC 240 v AC

Frequency 50/60 Hz 50/60 Hz

Idle Current 3.5 A¹ 1.75 A²

Max. Operating Current 4.5 A¹ 2.25 A²

Max Surge Current 5.0 A¹ 2.52 A²

Circuit Breaker 3.0 A per unit³

¹ Typical current at 120 v AC, 60 Hz (assumes 0.72 power efficiency, 0.99 power factor).

² Typical current at 240 v AC, 60 Hz (assumes 0.72 power efficiency, 0.99 power factor).

³ Recommend a dedicated line with no more than four 120 v AC units per 20 amp circuit.

Site Wiring and Power Considerations

The controller module is a nominal 90 v AC to 264 v AC, 50/60 Hz unit that meetsstandard voltage requirements for both domestic (USA) and international (outsideUSA) operation. It uses standard industrial wiring with a line-to-neutral or line-to-linepower connection (Table 13 on page 40).

Consider the following when preparing the site and cabinet for installation:


v AC power source . The AC power source must provide the correct voltage,current, and frequency specified on the manufacturer’s nameplate. Internal ACdistribution boxes (such as the cabinet’s power units) must be able to handle thepower requirements for this unit (Table 11 on page 39). You must have anindependent AC power source for each power supply in the controller module inorder to maintain redundancy.

v Earth ground . There must be an earth ground conductor on the AC powersource.

v Circuit overloading . Make sure the power circuits and associated circuitbreakers in both the cabinet and building provide sufficient power and overloadprotection. To prevent possible damage to the unit, isolate its power source fromlarge switching loads (such as air conditioning motors).

v Power interruptions . The controller module will withstand the following appliedvoltage interruptions:

– Input transient: 50% of nominal voltage

– Duration: one half cycle for the controller module; one full cycle for the drivemodule

– Minimum frequency: once every 10 seconds

v Power failures — Once power is restored after a complete power failure, theunit will automatically perform a power-up recovery sequence without operatorintervention.

Table 13. Site Wiring Voltages

Input Power Connection 50 Hz 60 HZ

Nominal Minimum Maximum Nominal Minimum Maximum

Single-Phase Line toNeutral

100 90 107 100 90 107

127 114 136 120 104 127

220 198 235

230 207 246

240 216 264

Single-Phase Line toLine

200 180 214 200 180 214

208 180 220

240 208 264

Power Cord Routing Notes

The controller and drive module each use two AC power cords (one for each powersupply).

The rackmount cabinet may have one or two AC Power Distribution Units (PDUs).Each PDU has its own power cord. Ideally, the redundant power supplies on thecontroller and device modules will each be connected to a separate PDU to provideAC power source redundancy. However, if the rack contains only a single PDU,then all power supplies will have to be connected to a single AC power source.

Additionally, if there are not enough PDU outlets for every power supply of all rackcomponents, then it will be necessary to use a Y power cable to connect two powersupplies to the same PDU outlet.

The power cabling priority should be:


1. There is at least 1 PDU outlet available for each module (controller, drive orhub) in the rack. This is the minimum requirement.

2. If there is only a single PDU in the rack, but an outlet is available, then eachcontroller module power supply should be connected to a different PDU outlet.

3. If there is only a single PDU in the rack and each controller module powersupply is connected to a separate PDU outlet and there are still outletsavailable, then each device module power supply should be connected to aseparate PDU outlet until no more outlets are available.

4. If there are 2 PDUs in the rack, then each controller module power supplyshould be connected to a different PDU.

5. If there are 2 PDUs in the rack and each controller module power supply isconnected to a different PDU and there are still outlets available, then eachdevice module power supply should be connected to a different PDU until thereare no more outlets available.

Interface Connectors and Cables

The controller module supports the following interface protocols:

v Host interface – Fibre Channel (copper wire or fiber optic), one per controller

v Drive interface – LVD-SCSI (low-voltage differential, small computer systeminterface), six drive channels

v Diagnostic interface – Ethernet or RS-232 (serial), one each per controller

Connectors and Host IDs

The host ID switches and connectors for interface cables are on the connector plate(Figure 3), located on the back of the controller module.

Figure 3. Interface Connections on Controller Module


Host and Drive ID Numbers

Each controller on a Fibre Channel loop must have a unique Fibre Host ID number.The host ID numbers assigned to each controller are based on two elements:

v Host ID numbers set through hardware switches on the controller module (seeFigure 3 on page 41). There are seven Host ID switches that allow you to set IDnumbers 0 through 127 for each controller. The factory default settings are ID #5for Controller A and ID #4 for controller B (see “Configuring the ControllerModule” on page 54).

v Software algorithms that calculate the actual Fibre Channel address, based onthe controller module’s hardware settings and position on the loop or hub.

There are also drive SCSI ID numbers that identify each controller to the LVD-SCSIdrives. Drive ID numbers are assigned to each controller at the factory and cannotbe changed. However, SCSI drive IDs on drive modules can be changed manually.Refer to Step 5 on page 51 under ″Installing the Drive Module″ for details on settingthe drive SCSI IDs.

Fibre Channel Host Cable Requirements

Table 14 lists the cable requirements for all Fibre Channel connections. For fiberoptic connections, you must use multi-mode, 50 micrometer fiber optic cable and aMedia Interface Adapter (MIA) shown in Figure 4.

Table 14. Fibre Channel Interface Cable Requirements

Cable Descriptions Order Information

Item Media Type Data Size Transfer Speed Range FRU Part No. Length

Fiber optic(multi-mode, 50micrometer)

Shortwavelaser

100 MB/sec 1062.5 Mbaud Up to 0.5kilometer

03K9202 5 meter

03K9204 25 meter

LVD-SCSI Drive Cable Requirements

To connect the controller module to a drive module, you must use 68-pin, VHDCI(very high density cable interface) LVD, Ultra SCSI-2 cables. The maximum lengthfor any SCSI cable is 25 m (82 ft.). Refer to “SCSI Cables” on page 194 for SCSIcable information. The controller module has six drive SCSI connectors that supportboth 8-bit and16-bit interface protocol. Each connector represents a single drivechannel that supports up to 10 drives per channel for a total of 60 drives. Refer to“LVD-SCSI Drive Cable Routing Examples” on page 59 for examples of connectingthe controller module to one or more LVD-SCSI drive modules. Table 15 on page 43lists the SCSI cable that you can use on this drive module.

Figure 4. Media Interface Adapter (MIA)


Table 15. Drive Module SCSI Interface Cable

Cable Part Number Length

O3K9195 2.0 meter

Preparing the Rackmount Cabinet

To prepare the rackmount cabinet for installation (Figure 5), review the appropriatechecklist and complete all applicable preparatory procedures.

Cabinet Preparation Task List

If you are installing a new IBM 2101-100 Seascape Solutions rack with the rackcomponents (controller module, drive modules and optional hubs) already installed,then use the following preparation checklist:

1. Move the rack to its final destination.

2. Unpack and set up the rack using the installation procedures in the SeascapeSolution Rack, Installation and Service Guide, IBM 2101 Model 100,SY27-7606.

Important: The rack must be able to support the weight of all devices that willbe installed, without tipping over. The rack may need to be securedusing a stabilizer plate, by being bolted to the floor, or by someother method specific to the rack being used and the installationsite. Refer to the rack documentation for more information.

3. If applicable, install the optional remote support switch and modem using theprocedures in “Remote Support Attachment of the WTI Data Switch andModem” on page 229.

4. Go to “Configuring the Controller Module” on page 54.

Figure 5. Rackmount Cabinet


If you are installing a new controller module and any other rack components into anexisting 19 inch compatible rack, then use the following preparation checklist:

1. Move the rack to its final destination.

2. Unpack and set up the rack using the installation procedures from theappropriate rack document.

3. Remove external rack panels, if applicable.

4. Stop all I/O activity to the existing devices in the rack, if applicable.

5. Turn off power to all devices in the rack and turn off the rack power.

6. Install the support rails for mounting the controller module and any drivemodules in the rack if they are not already installed. See “Installing the SupportRails”.

7. Install the controller module in the rack. See “Installing the Controller Module”on page 45.

8. Install the drive modules in the rack. See “Installing the Drive Module” onpage 49.

9. If applicable, install any rackmount hubs in the rack using the installationprocedures in Fibre Channel Storage Hub, Installation, Service, and User’sGuide, IBM 2103 Model H07, SC26-7289.

10. If applicable, install the optional remote support switch and modem using theprocedures in “Remote Support Attachment of the WTI Data Switch andModem” on page 229.

11. Go to “Configuring the Controller Module” on page 54.

Installing the Support Rails

About Support Rails

To install the controller module or drive modules in a rackmount cabinet, you needthe appropriate rackmount support rail kit.

Where you place the support rails in the cabinet depends on where you intend toposition the controller or device modules in the cabinet. In a standard configuration,the controller module is installed at the top of the rack and device modules areinstalled beginning at the bottom of the rack and moving upwards. If you are usinga different type of mounting system, refer to the documentation shipped with yourcabinet hardware.

Note: If your cabinet already has a set of support rails installed at the positionwhere you are installing the controller or drive modules, you may skip to thenext task.

Instructions

Use this procedure only if you need to install mounting hardware in a cabinet beforeinstalling a controller or drive module. These instructions assume that you arefollowing the cabinet preparations task list in “Cabinet Preparation Task List” onpage 43. Make sure that you have a minimum of two feet around the outside of thecabinet in order to install the support rails and complete the remaining installationprocedures.


1. Turn off the power, if applicable.

Stop all I/O activity to the devices in the cabinet in which you are installing thecontroller module. Turn off the power switches on both AC distribution boxes inthe cabinet.

2. Install the support rails.

If instructions were shipped with the support rail kit, then follow thoseinstructions for installing the support rails. If you are installing more than onerack module, you must install support rails for each unit.

a. Loosen the adjustment screws on both side rails and adjust them to fit therack.

b. Use the front alignment pins to line up the front of the rails with the rackmounting holes. The alignment pins are designed to allow installation into avariety of racks, so you may have to remove the alignment pins that do notalign correctly with the holes in the rack you are using.

c. Secure the side rails to the rack cabinet with the mounting hardware.

v Use eight screws with nuts for the controller rails (two in the front and twoin the back of each rail).

v Use six screws with nuts for the drive drawer rails. Use only one screw inthe front lower mounting hole for now – the second screw will be usedwhen the drive drawer is installed.

Make sure that both side rails are parallel and level with one another inthe rack cabinet.

v Tighten the rail adjustment screws.

3. Go to the next task.

End of Procedure

Installing the Controller Module

Tools and Equipment

Antistatic wrist strap, screwdrivers, Host Fibre interface cables and MIA, DriveLVD-SCSI cables, optional Secondary interface cables (RS-232 or Ethernet), tiewraps and a cart or level surface (to hold the FRUs).

Instructions

Use this procedure to install a controller module on the support rails in a rackmountcabinet. These instructions assume that you are following the cabinet preparationstask list in “Cabinet Preparation Task List” on page 43.

1. Check the contents of the shipping container.

The controller module shipment should include:

v Power cords. These attach the controller module to the AC power sourcesinside the cabinet.

v Other items. Depending on how you ordered the controller module, otheritems may be included, such as storage management software (CD ordiskettes), interface cables, 16-bit terminators, mounting hardware, oradditional documentation. Refer to the shipping list or invoice included withthe controller module for a complete list of items.


2. Remove the front cover from the controller module (Figure 6).Attention: Electrostatic discharge can damage sensitive components. Use agrounding wrist strap or other antistatic precautions before removing orhandling any components in the cabinet.

3. Remove all the FRUs, using Figure 7, Figure 8 on page 47 and Figure 9 onpage 47 as a guide.

Figure 6. Removable Covers on the Controller Module

Figure 7. Removing The FRUs


4. Put the controller module in the cabinet (Figure 10 on page 48).

At front of the cabinet, set the controller module on the support rails and slideit to the back of the cabinet.

5. Secure the controller module (Figure 10 on page 48).

Figure 8. Removing The FRUs – cont.

Figure 9. Removing The FRUs – cont.


Align the controller module chassis holes with the mounting holes on the sideof each rail. Insert a self-tapping screw into the mounting holes on the side ofeach rail and tighten. Use only the holes designated in Figure 10 to mount thecontroller module. Attention: Electrostatic charge can damage sensitivecomponents. Use a grounding wrist strap or other antistatic precautionsbefore handling any components in the cabinet.

6. Replace all FRUs that you removed in Step 3 on page 46.

Reverse the instructions shown in Figure 7 on page 46, Figure 8 on page 47and Figure 9 on page 47 to install the controllers, controller fan, battery, powersupplies, and power supply fan into the chassis. As you install the FRUs, makesure that you lock all FRUs securely in place.

Note: The power supplies are interchangeable, so you can insert them ineither slot.

7. Connect the LVD- SCSI drive cables (Figure 11 on page 49).

Attach LVD-SCSI drive cables to the drive LVD connectors on the controllermodule.

Figure 10. Chassis Mounting on Support Rails


8. If applicable, attach secondary interface cables (Figure 11).

There is one RS-232 and one Ethernet connector for each controller. Attachcables to these connections if you need to perform troubleshooting, specialconfiguration tasks or you are connecting the controller to a network RAIDstorage Management PC.

9. Route and secure the Fibre Channel interface cables. If all the drive modulesare already installed and connected, then also route and secure the SCSIinterface cables.

Arrange the interface cables so they clear the vents on the back of thecontroller module. Secure the cables with tie-wraps.


End of Procedure

Installing the Drive Module

Tools and Equipmentv Antistatic wrist strap or other antistatic protection device

v screwdrivers

v all drive module FRUs

v Table or counter-top to hold FRUs

Instructions

Use this procedure to install a drive module on the support rails in a rackmountcabinet. These instructions assume that you are following the “Cabinet PreparationTask List” on page 43.

Attention: Electrostatic discharge can damage sensitive components. Use agrounding wrist strap or other antistatic precautions before removing or handlingany components in the cabinet.

1. To reduce weight, remove the drive FRUs from the drive module, usingFigure 12 on page 50 and Figure 13 on page 51 as a guide.

Figure 11. Interface Connections on a Rackmount Controller Module


Be sure to keep track of which drive you remove from which location. You mustreplace the drives in the exact slots from which you removed them.

Figure 12. Removing the Drive Module FRUs


2. Put the Drive Module in the cabinet.

At the front of the cabinet, set the Drive Module on the support rails and slide itto the back of the cabinet.

3. Secure the Drive Module.

Align the front holes on each side of the chassis with the holes on the front ofthe support rails. Secure the front of the chassis to the cabinet rails by insertingscrews through the bezel and into the holes on each side. Secure the back ofthe Drive Module to the support rails with two screws, one on each side (SeeFigure 92 and Figure 93 on page 177). Attention: Electrostatic discharge candamage sensitive components. Use a grounding wrist strap or other antistaticprecautions before handling the FRUs.

4. Replace all of the FRUs that you removed in Step 1 on page 49.

Reinstall the drives, fans, power supplies, and ESM board FRU into the chassisin reverse order that you removed them in Step 1 on page 49. Make sure thatyou install the drives in their correct slots, and lock all FRUs securely into place.

Note: The power supplies and fans are interchangeable, so you can insertthem in either slot as long as you:

v Make sure that the lever opens in the correct direction. The powersupplies have reversible left and right levers. The lever on the leftpower supply opens to the right; the lever on the right power supplyopens to the left.

v Make sure that the fans are in the correct orientation before youattempt to install them (see Figure 12 on page 50).

5. Set the Drive Module Interface Options.

Figure 13. Removing the Drive Module FRUs – cont.


There is a Tray ID switch and a set of Option switches on the back of theDrive Module that are used to select interface options, and to determinewhether these drives are configured as two 5-drive buses or one 10-drive bus(see Figure 14 on page 53). These switches should be set as follows:

v Tray ID:

This switch is used to identify the drive module based on its location in therack. The rack will support up to six drive modules and the tray ID must beunique for each. Drive Modules should be installed beginning at the bottom ofthe rack, moving upward with each succeeding Drive Module installation.

Set the Tray ID of the first (bottom most) Drive Module to ″1″, set the secondDrive Module Tray ID to ″2″, and so on, proceeding to the sixth Drive Module(Tray ID=″6″), installed immediately below the Controller Module. This is afully populated rack.

v Option Switches:

These switches are used to set the interface options and set the SCSI IDs ofthe drives in the Drive Module. Unless instructed otherwise, you should onlyhave to change Switch 1, the Bridge Disable bit. All other option switchesshould be in the ″OFF″ position (see “Factory Settings” on page 191 for moredetail about Option Switches).

When the Bridge Disable switch (Switch 1) is in the ″ON″ position, the DriveModule acts as two independent 5–drive buses with one SCSI connection toeach bus. When this switch is ″OFF″, the Drive Module acts as one 10–drivebus with two SCSI connections (see “Drive Numbering” on page 144).

The setting of this switch is determined by the number of drive modulesinstalled in the rack:

a. 1, 2 or 3 drive modules installed: The Bridge Disable bit (switch 1)should be in the ″ON″ position for all drive module and each moduleshould have two SCSI connections to the controller module.

b. 4 drive modules installed: The Bridge Disable bit (switch 1) should be inthe ″ON″ position for drive modules 2 and 3 (the second and third drivemodules from the bottom of the rack), and ″OFF″ for drive modules 1 and4. Drive modules 2 and 3 will each have two SCSI connections to thecontroller module, and drive modules 1 and 4 will each have a singleSCSI connection to the controller module.

c. 5 drive modules installed: The Bridge Disable bit (switch 1) should be inthe ″ON″ position for drive module 3 (the third drive modules from thebottom of the rack), and ″OFF″ for drive modules 1, 2, 4 and 5. Drivemodule 3 will have two SCSI connections to the controller module, and allthe rest will have a single SCSI connection to the controller module.

d. 6 drive modules installed: The Bridge Disable bit (switch 1) should be inthe ″OFF″ position for all drive module and each module will have singleSCSI connections to the controller module.

See “LVD-SCSI Drive Cable Routing Examples” on page 59 for examples.


6. Connect the Cables

There are two SCSI interface connectors on the ESM board (Figure 15 onpage 54) for attaching the SCSI cables from the controllers to the Drive ModuleSCSI buses. Depending on the setting of the Bridge Disable switch (OptionSwitch 1), you will have to connect either one or two SCSI cables between thecontroller and drive modules:

v If the Bridge Disable switch is in ″ON″ position: Connect two cables, oneto each connector on the ESM board.

v If the Bridge Disable switch is in ″OFF″ position: Connect one SCSI cableto the Bus 1 one connector (left connector when viewed from the back) onthe ESM board.

Attach the SCSI interface cables from the controller module to the SCSIconnectors on the ESM board.

7. Route and secure the SCSI interface cables.

Arrange the interface cables so that they clear the vents on the back of themodule. Secure the cables with tie-wraps.

8. Connect the power cords (Figure 15 on page 54).

Read “Power Cord Routing Notes” on page 40. Make sure both power switchesare turned off and connect both power cords to the drive module.

Figure 14. Tray ID and Option Switches



Configuring the Controller Module1. Set the Fibre Host IDs (Figure 16 on page 55).

Each controller on a Fibre Channel loop must have a unique Fibre Host IDnumber (refer to “Host and Drive ID Numbers” on page 42). The Fibre Host IDswitches are located on the back of the controller module (upper right corner).The Host ID settings determine the SCSI ID of the individual controllers on theFibre channel loop as described in the table below. If you need to change thecontroller’s host ID setting, move the switches up or down.

As there are 127 valid switch settings, it is recommended that each controllerhave a unique address selected from the following table:

Host ID SettingController SCSI ID

Hex Binary (switch setting)

04 0 0 0 0 1 0 0 E1

05 0 0 0 0 1 0 1 E0

06 0 0 0 0 1 1 0 DC

07 0 0 0 0 1 1 1 DA

08 0 0 0 1 0 0 0 D9

09 0 0 0 1 0 0 1 D6

0A 0 0 0 1 0 1 0 D5

0B 0 0 0 1 0 1 1 D4

0C 0 0 0 1 1 0 0 D3

0D 0 0 0 1 1 0 1 D2

0E 0 0 0 1 1 1 0 D1

0F 0 0 0 1 1 1 1 CE

10 0 0 1 0 0 0 0 CD

Figure 15. Connecting Interface Cables and Power Cords


Host ID SettingController SCSI ID

Hex Binary (switch setting)

11 0 0 1 0 0 0 1 CC

12 0 0 1 0 0 1 0 CB

13 0 0 1 0 0 1 1 CA

14 0 0 1 0 1 0 0 C9

15 0 0 1 0 1 0 1 C7

16 0 0 1 0 1 1 0 C6

17 0 0 1 0 1 1 1 C5

18 0 0 1 1 0 0 0 C3

19 0 0 1 1 0 0 1 BC

1A 0 0 1 1 0 1 0 BA

1B 0 0 1 1 0 1 1 B9

1C 0 0 1 1 1 0 0 B6

1D 0 0 1 1 1 0 1 B5

1E 0 0 1 1 1 1 0 B4

1F 0 0 1 1 1 1 1 B3

On subsystems connected to AIX hosts, the controller SCSI ID is used toidentify the controllers (DACs) in the subsystem when configuring thesubsystem or reporting errors. You can use this table to map the reported SCSIID to an individual controller based on its Host ID setting.

2.

Verify that the Media Interface adapters are securely attached to the fibrechannel connectors (J3 and J4) on the back of the controller module (Figure 11on page 49

Figure 16. Setting the Fibre Host IDs


on page 49). Attention: Bending or damaging Fibre Channel cables couldresult in degraded performance or data loss. Do not pinch the cables with tiewraps. Do not make sharp bends when routing the cables. Do not step on thecables or locate them in aisles or walkways.

3. Attach the host Fibre Channel cables (Figure 11 on page 49).

Attach the Fibre Channel cable from host adapter 1 to connector J3 (Fiber HostBD 1) on the back of the controller module. Attach the FC cable from hostadapter 2 to connector J4 (Fiber Host BD 2).

Completing the Installation

Start-up Notesv Adding a new 2102 RAID subsystem to an existing storage environment is

non concurrent. If you are adding this 2102 RAID storage subsystem to anexisting installation (for example, you are connecting a second 2102 subsystemto an existing host), you must stop all activity from the existing host(s) and rebootthem in order to add the new subsystem.

v You must power up the drive modules before powering up the controllermodule. Controller modules will not acknowledge any attached drives that areinitially powered up after the controller module.

v The controller and drive modules have light emitting diodes (LEDs) that indicatethe status of both the overall modules and the individual components within theunit. Check all LEDs on the controller and drive modules (front and back) whenyou power up the unit to make sure there are no problems.

Configuration Notes

Once the controller module hardware is installed and turned on, you may need toperform certain tasks to complete the installation. These tasks may include:

v Verifying the installation

v Updating controller firmware

v Updating drive firmware

Starting Up the Subsystem

Tools and Equipment

Power cords (2) shipped with controller module

Instructions

Use these instructions to connect the controller module power cords, turn on thepower, and check the subsystem status.

1. Read “Power Cord Routing Notes” on page 40. Go to Step 2.

2. Make sure that both power switches on the controller module are turned off(Figure 17 on page 57).

3. Plug both power cords into the controller module (Figure 17 on page 57).

4. Plug power cords into the AC outlets.


If possible, plug each controller power cord into an independent power source tomaintain power redundancy (see “Power Cord Routing Notes” on page 40).

5. Turn on the power as follows:

a. Rack: The rack power is active when each Power Distribution Unit (PDU)power cord is plugged into the external power source. A green light on thePDU indicates that power is active to that PDU.

b. Hub (if applicable): Hub power is active when the hub power cord isplugged into the rack or external power source.

c. Drive Modules: Turn on both power switches on the back of each drivemodule (see Figure 18). During the power-up process, the Drive ModuleLEDs may turn on and off intermittently. When power-up is complete, thegreen power LEDs will be on and all amber LEDs should be off.

d. Controller Module: Turn on both power switches on the back of theController Module (see Figure 17). The controller module may take fromthree to ten seconds to power-up. During this time, the Controller ModuleLEDs may turn on and off intermittently.

Figure 17. Controller Module Power Cords and Power Switches

Figure 18. Drive Module Power Switches


Once the Controller Module has powered up, the controllers will spin up thedrives in the drive modules. Depending on the number of drives in thesubsystem, this process could take several minutes to complete.

e. Host: Have the customer power up or reboot the host system, to allowrecognition of the array.

6. Check the controller and drive modules for faults.

Go to “Using the Status LEDs” on page 75 and follow the instructions for checkthe controller module’s status. If any Fault LEDs turn on and remain on, refer tothe appropriate page listed in Table 16 on page 76 and Table 17 on page 78.

Go to “Check the Overall Hardware Status” on page 156 and follow theinstructions for checking the drive modules’ status. If any fault LEDs come onand remain on, refer to the appropriate Service Page listed in Table 33 onpage 157 and Table 34 on page 158.

7. Replace the controller module front cover (Figure 6 on page 46).

8. Go to “Verifying the Installation”.

End of Procedure

Verifying the Installation

Tools and Equipment

You will need access to the Fibre Channel Storage Manager host software.

Instructions

Use this procedure as a guideline for verifying the subsystem configuration.

1. Read “Configuration Notes” on page 56.

2. Verify the installation using the Fibre Channel Storage Manager host software.

Some default software parameters (such as RAID level, drive groups, andcaching) are set at the factory before shipment. If Fibre Channel StorageManager software is already installed on the host, use it to check the currentsoftware configuration for both the controllers and drives and to verify that bothcontroller boards and all drives can be seen by the host. You may also need tochange the mode of the controllers from active/passive to active/active.Refer to the appropriate software documentation for instructions on using thesoftware.

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host, thenuse the Configuration application to verify that both controller boards and alldrives can be seen by the host. Refer to Fibre Channel Storage Manager andStorWatch Fibre Channel RAID Specialist, User’s Guide for instructions onusing the software.

v If the subsystem is attached to an AIX host system, use the Disk ArrayManager to verify that both controller boards and all drives can be seen bythe host. Refer to Fibre Channel Storage Manager, Installation and User’sGuide for the AIX Operating System for instructions on using the software.

Note: The controller module, drive units, or other components in your systemmay be identified by names that differ from those used in this book. Keepthis in mind when using the software.

3. Begin normal system operation.


End of Procedure

Removal

If you are removing the subsystem from service, you must be sure to erase anyuser data on the array. Have the customer use the Storage management softwareto format all existing LUNs and then delete the configuration. If the host connectionis not available or already disconnected, you can use DOS RAID Manager (DRM)to perform these operations. Make sure the customer understands that all data willbe lost and unrecoverable. If drive drawers are being moved to another subsystem,you must remove the configuration information written on the drives to avoidproblems. Make sure that all the drives in the drawer being used are ″unassigned″(not part of any drive groups or LUNs) before moving.

Important: If the ″Reset Configuration″ option is used to delete the configurationinformation on the drives, be aware that this function results in thecreation of a default LUN 0. You must delete this LUN after the resetconfiguration function completes.

LVD-SCSI Drive Cable Routing Examples

Use the following examples for connecting a controller module to one or moreLVD-SCSI drive modules. Rackmount cabling examples begin on “Drive CablingExample A”.

Note: Drive numbers are shown in decimal in the following examples. Some hostor service utilities may display these values in hexadecimal format.

Drive Cabling Example A

Drive Cabling Example A shows the cabling configuration for one drive module:


Drive Cabling Example B

Drive Cabling Example B shows the cabling configuration for two drive modules:

Configuration:

v One (1) Controller Module

v One (1) Drive Module

v Bridge Disable = ON

Figure 19. Rackmount Cabling to One Drive Module


Drive Cabling Example C

Drive Cabling Example C shows the cabling configuration for three drive modules:

Configuration:


v Two (2) Drive Modules

v All Bridge Disables = ON

Figure 20. Rackmount Cabling to Two Drive Modules


Drive Cabling Example D

Drive Cabling Example D shows the cabling configuration for four drive modules:

Configuration:


v Three (3) Drive Modules

v All Bridge Disables = ON

Figure 21. Rackmount Cabling to Three Drive Modules


Drive Cabling Example E

Drive Cabling Example E shows the cabling configuration for five drive modules:

Configuration:


v Four (4) Drive Modules

v Bridge Disable = OFF on Drive Modules D1 and D4

v Bridge Disable = ON on Drive Modules D2 and D3

Figure 22. Rackmount Cabling to Four Drive Modules


Drive Cabling Example F

Drive Cabling Example F shows the cabling configuration for six drive modules:

Configuration:


v Five (5) Drive Modules

v Bridge Disable = OFF on Drive Modules D1, D2, D4 and D5

v Bridge Disable = ON on Drive Module D3

Figure 23. Rackmount Cabling to Five Drive Modules


Configuration:


v Six (6) Drive Modules

v All 6 Bridge Disables = OFF

Figure 24. Rackmount Cabling to Six Drive Modules


Part 3. Controller Module Service Guide


Chapter 3. Getting Started

Identifying the Parts

This section provides brief descriptions and reference pages for the controllermodule’s primary components.

Controller Module Cabinets

The Controller Module is a rackmount unit (Figure 25):

Removable Components

The controller module contains several removable, portable canisters, called fieldreplaceable units (FRUs, pronounced “frews”), that you can access from either thefront or back of the unit. These FRUs include: a battery, controllers, power supplies,and cooling fans. The controller module has a removable front cover.

Front View

The front of the controller module has the following primary components (Figure 26on page 70):

v Front cover – a removable panel with holes for viewing the status lights and forboosting air circulation. See “Gaining Access to the Controls” on page 72.

v Controller FRUs – two removable units that contain array controllers. See“Controller Description” on page 89.

v Battery FRU – one removable unit that contains batteries and battery chargercircuitry. See “Battery Description” on page 112.

v Controller fan FRU – one removable unit that contains two cooling fans. See“Controller Fan Description” on page 103.

Figure 25. Rackmount Cabinet


Back View

The back of the controller module has the following primary components(Figure 27):

v Connector plate – a protective panel that contains access holes for interfaceconnectors and jumpers. See Figure 27.

v Power supply FRUs – two removable units for the power supplies. See “PowerSupply Description” on page 118.

v Power supply fan FRU – one removable unit for the cooling fans. See “PowerSupply Fan Description” on page 107.

Internal Components

Inside the chassis, the controller module has the following primary components(Figure 28 on page 71 and Figure 29 on page 71):

Figure 26. Front View of Controller Module

Figure 27. Back View of Controller Module


v Controller card cage – a modular structure inside the chassis consisting ofcontroller shelves and the controller backpanel. See “Controller BackpanelDescription” on page 96.

v Power supply assembly – a modular structure inside the chassis consisting ofthe power interface board and slots for holding the power supply and powersupply fan FRUs. See “Power Interface Board Description” on page 130.

v Power harnesses – internal cables that connect the components to thecontroller backpanel and power interface board. See “Battery HarnessDescription” on page 123 and “DC Power Harness Description” on page 126.

Figure 28. Internal Components

Figure 29. Internal Components – cont.

Chapter 3. Getting Started 71

Basic Operation

The controller module has several features that aid in operating and servicing thehardware. These include:

v LEDs (light emitting diodes) – green or amber lights that glow or blink to indicateeither a normal operating status or hardware error

v Power switches – two switches that turn the controller module’s power off andon

v Handles and levers – allow you to remove and install individual FRUs moreeasily

v Connectors – sockets for attaching interface and power cables to the controllermodule

This section explains how to use these controls to turn the controller module on andoff under normal and emergency circumstances. It also explains how to check thecontroller module’s hardware status.

Gaining Access to the Controls

To gain access to the controller module’s FRUs, cables, LEDs, and switches, youmust remove the front cover. Figure 30 shows you how to remove the cover.

Turning On the Power

Note: If you are turning on the controller module after an emergency shutdown orpower outage, use the procedure “Restoring Power” on page 74.

Instructions

Use this procedure to power-up to the controller module. For instructions onpowering-up the drive modules, refer to “Chapter 9. Operating the Drive Module” onpage 153.

Figure 30. Removable Cover on the Controller Module


Important: You must turn on the drive modules first before turning on the controllermodule. The controllers will not acknowledge any attached drives thatare powered up after the controller module.

When are you turning on the controller module?

v After a normal shutdown . Turn on both power switches on the back of thecontroller module (Figure 31). You must turn on both switches to take advantageof the redundant power supplies. Then, go to “Using the Status LEDs” onpage 75.

v At initial start-up . Verify the following:

– All cables and FRUs are plugged securely into the controller module.

– The host IDs are set correctly.

– The hosts and other devices are ready for power-up.

Check the documentation for other devices attached to the system and determinethe proper start-up sequence for all applicable devices.

Based on this power-up sequence, turn on the power to each device, includingapplicable circuit breakers in rackmount cabinets. When it is time, turn on bothcontroller module power switches (Figure 31).

Go to “Using the Status LEDs” on page 75.

End of Procedure

Figure 31. Controller Module Power Switches


Turning Off the Power

Attention: Except in an emergency, never turn off the power if any Fault LEDs arelit on the controller module. Always correct the fault by using the propertroubleshooting or servicing procedure before turning off the power. This will ensurethat the controller module will power up correctly later. For guidance, refer to“Troubleshooting Quick Reference” on page 133.

Instructions

Use this procedure to turn off the controller module’s power. The controller moduleis designed to run continuously, 24 hours a day. Once you turn on the controllermodule, it should remain on except during certain service procedures.

1. Prepare the controller module for shutdown.

a. Stop all I/O activity to the controller module and attached drivemodules. If applicable, logically disconnect the controllers and drivemodules from the hosts. Make sure that the Fast Write Cache LED on thefront cover and all applicable drive activity LEDs are off (not blinking).

b. Make sure that all amber Fault LEDs on the controller module are off. Ifany Fault LEDs are lit, correct the problem before you turn off the power(see “Using the Status LEDs” on page 75).

2. Turn off the power switches (Figure 31 on page 73).

Turn off both power switches on the back of the controller module. If you wantto shut down the entire system, turn off power to the rack.

End of Procedure

Restoring Power

Note: Never turn on the power to any equipment when there is evidence of fire,water, or structural damage.

Instructions

Use this procedure to restart the controller module after a power failure oremergency shutdown.

1. After the emergency situation is over or power is restored to the building, checkall components and cables for damage.

DO NOT continue with this procedure if you find any evidence of fire, water, orstructural damage. If there is no visible damage, go to the next step.

If there is evidence of damage, call the factory or appropriate serviceorganization for assistance. Depending on the current service agreements, youmay or may not need to send the unit back to the factory for repair/replacement.

2. Plug in the power cords and turn on the power (Figure 31 on page 73).

a. After checking for physical damage, plug in the power cords.

b. Turn on the power switches on all drive modules attached to the controllermodule. If applicable, turn on the circuit breakers in the rackmount cabinet.

c. Next, turn on both power switches on the back of the controller module

3. Check the status of the controller module and other devices.


Make sure all Fault LEDs are off on the front and back of the controller module(see “Using the Status LEDs”). Once all the devices on the system arepowered-up, check the overall system status using the storage managementsoftware.

4. Replace the front cover (Figure 30 on page 72).

End of Procedure

Using the Status LEDs

The controller module’s LEDs indicate the status of the controller module and itsindividual components. The green LEDs indicate a normal operating status; amberLEDs indicate a hardware fault. It is important that you check all of the LEDs on thefront and back of the controller module when you turn on the power.

In addition to checking for faults, you can use LEDs on the front cover, controllerFRUs, and drive units (if applicable) to determine if the controllers and drives areresponding to I/O transmissions from the host. Refer to your storage managementsoftware user’s guide for additional information about checking system status.

Consider the following LED activities when you check LED statuses:

v If a Fast Write Cache operation or other I/O activity is in progress to thecontroller module (or attached drive units), you may see several green LEDsblinking, including: the Fast Write Cache LED (on the front cover), controller FRUstatus LEDs, or applicable drive activity LEDs.

v The green Heartbeat LEDs on the controller FRUs blink continuously. Thenumber and pattern of green status LEDs lit on the controllers depend on howyour system is configured. An active controller will not have the same statusLEDs lit as a passive controller.

v If you just turned on the power, the controller module’s green and amber LEDsmay turn on and off intermittently. Wait until the controller module finishespowering up before you begin checking for faults.

Instructions

Use this procedure to check the LEDs and operating status of the controller moduleand its components. For additional information on status LEDs, refer to “ControllerFan Description” on page 103. For troubleshooting instructions, go to“Troubleshooting Quick Reference” on page 133.

1. Remove the cover (Figure 30 on page 72).

To view the controller FRU LEDs, you must remove the front cover from thecontroller module.

2. Check the LEDs on the front.

Use Figure 32 on page 76 and Table 16 on page 76 to check the status LEDson the front of the controller module. Under normal conditions, the green PowerLED (top or left light) is on and the amber LEDs are off. If any amber LEDs areon, go to the service page indicated in the last column of Table 16 on page 76,otherwise go to Step 3 on page 77.


Table 16. Status LEDs on Front of Controller Module

Location LED LED Color Normal Status Problem Status See:

Front Cover(controller fan FRU)

Power Green On Off “TroubleshootingPower SupplyProblems” onpage 120

Power Supply Amber Off On “TroubleshootingPower SupplyProblems” onpage 120

Fan Amber Off On “Determining WhichFan Failed” onpage 102

Controller Amber Off On “TroubleshootingController Problems”on page 92

Fast Write Cache Green Blinking¹ Off¹ See footnote¹

Figure 32. LEDs on the Front


Table 16. Status LEDs on Front of Controller Module (continued)

Location LED LED Color Normal Status Problem Status See:

Controller FRU Fault Amber Off On “TroubleshootingController Problems”on page 92

Power Green On Off “TroubleshootingController Problems”on page 92

Heartbeat Green Blinking² Off Table 18 on page 90and “TroubleshootingController Problems”on page 92

Status Green F0000000 orF1101110²

any otherpattern²

Table 18 on page 90and “TroubleshootingController Problems”on page 92

Battery FRU Fault-B Amber Off On “TroubleshootingBattery Problems” onpage 114

Full Charge-B Green On Off “TroubleshootingBattery Problems” onpage 114

Fault-A Amber Off On “TroubleshootingBattery Problems” onpage 114

Full Charge-A Green On Off “TroubleshootingBattery Problems” onpage 114

¹ Fast Write Cache LED blinks only during a fast write operation. Refer to the host RAID management software fordetails about using Fast Write Cache.

² There are eight status LEDs, the Heartbeat and seven others. The number and pattern of the green status LEDsthat are in the ″ON″ state depends on how your system is configured (F = flashing; 1 = ON; 0 = Off). Refer to Table 18on page 90 for details.

3. Check the LEDs on the back.

Use Figure 33 on page 78 and Table 17 on page 78 to check the status LEDson the back of the controller module. All green LEDs should be on and theamber Fault LED should be off. If the Fault LED is on or one of the green LEDsis off, go to the service page indicated in the last column of Table 17 onpage 78, otherwise proceed to Step 4.


Table 17. Status LEDs on Back of Controller Module

Location LED LED Color Normal Status ProblemStatus

See Page

Power Supply FRU Power Green On Off “TroubleshootingPower SupplyProblems” onpage 120

Power Supply Fan FRU

Fault Amber Off On “TroubleshootingPower SupplyFan Problems” onpage 109

Power Green On Off “TroubleshootingPower SupplyFan Problems” onpage 109

4. With all status LEDs indicating a “normal status,” replace the front cover.

End of Procedure

Instructions for Modifying the Controller Module

You may need to make changes to the controller module under the followingcircumstances:

v Moving the controller module to a new location (refer to Preparing to Move theController Module below)

v Removing the controller module from its cabinet in order to service internal parts(refer to Preparing to Move the Controller Module)

You can use the instructions in this section to disassemble and reassemble all orpart of the controller module in order to move, modify, or service its parts.

Figure 33. LEDs on the Back


Preparing to Move the Controller Module

Perform the following preparatory tasks before moving the controller module to anew location or before removing it from its cabinet. These will help safeguard theequipment and help ensure a smoother transition to the new environment. Thesetasks include:

v Always make sure that all I/O activity to and from the controller module hasstopped.

v Shut down all devices in the rackmount cabinet before moving it to the newlocation.

v If you are moving the controller module over any significant distance, pack it inits original shipping container for safe transit.

Removing and Installing FRUs

Tools and Equipment

Antistatic protection and a cart or level surface (on which to place the FRUs)

Instructions

Use this procedure to remove one or more FRUs from a controller module.

1. Remove the front cover (Figure 30 on page 72).

2. Stop all activity to the controller module.

Stop all system processes and I/O activity to the controller module and clear alldata from cache memory (refer to the software documentation for instructions).Make sure:

v That all activity LEDs on the drives are not blinking

v That all fault LEDs and the Fast Write Cache LED on the controller moduleare off

3. Put on a grounding strap, turn off both power switches, and unplug the powercords from the controller module. Then, go to the next step.Attention: Electrostatic charges can damage sensitive components. Use properantistatic precautions before removing or handling the FRUs.

4. Using Figure 34 on page 80, Figure 35 on page 80 and Figure 36 on page 81 asa guide, remove the FRUs.

5. What do you want to do now?

v Remove the controller module from its cabinet. Go to “Removing theModule from the Rackmount Cabinet” on page 81 and complete the removalprocedure. To reinstall the FRUs, reverse steps 1 through 4 in this procedure.

v Complete a service procedure. Return to the appropriate procedure (forexample: “Replacing the Battery Harness” on page 125 or “Replacing the DCPower Harnesses” on page 128) and continue with the service instructions.To reinstall the FRUs, reverse steps 1 through 4 in this procedure.

End of Procedure


Figure 34. Removing and Installing FRUs

Figure 35. Removing and Installing FRUs – cont.


Removing the Module from the Rackmount Cabinet

Tools and Equipment

Screwdrivers, antistatic protection, and cart or level surface (to hold the controllermodule chassis and FRUs)

Instructions

Use this procedure to remove the controller module from the rackmount cabinet.

1. Complete all the instructions in “Removing and Installing FRUs” on page 79,then continue at Step 2 on this page.

2. Disconnect the interface cables (Figure 37 on page 82).

a. Disconnect and label all drive SCSI cables from the controller module(drive channel #1, drive channel #5, etc.).

b. Disconnect and label the host Fibre Channel cables (host #1 and host #2).

Attention: Bending or damaging Fibre Channel cables can result in degradedperformance or data loss. Make sure the cables are not pinched, bent, nicked,or pulled during the installation.

Fiber optic cables are very fragile. When working with fiber optic cables, do notpinch them with tie wraps, step on them, or bend cables at sharp angles.Maintain a bend radius of more than 30.5 millimeters (1.2 inches).

Figure 36. Removing and Installing FRUs – cont.


3. Remove the controller module chassis (Figure 38).

Remove the four screws (two in front, two in back) that secure the controllermodule to the side rails. From the front of the cabinet, pull the chassis out of thecabinet. Set it on a level, dry surface.

4. Service, move, or ship the controller module by choosing one of the following:

v If you are performing a service procedure , return to the appropriate pageand complete the instructions. When you are finished servicing the controllermodule, you can reinstall it into the cabinet by reversing the steps in thisprocedure.

v If you are moving the controller module to another rackmount cabinet ,remove the support rails and power cords from the old cabinet and installthem in the new one. Then, install the controller module by reversing thesteps in this procedure. Refer to “Chapter 2. Installation And Removal Guide”on page 35 for instructions on installing the controller module.

Figure 37. Disconnecting Interface Cables

Figure 38. Removing and Installing the Chassis on Support Rails


v If you are shipping the controller module to another location, replace allof the FRUs in the controller module. Carefully wrap and pack the unit in itsoriginal shipping material and container.

End of Procedure

Disassembling and Reassembling the Chassis

Tools and Equipment

Antistatic protection and screwdrivers

Instructions

Use this procedure to completely or partially disassemble (and reassemble) thecontroller module’s chassis in order to service its internal components.

1. Remove the controller module from the cabinet. When you have the chassisout of the cabinet, set it on a dry, level surface (battery side down) as shown inFigure 39.

2. Remove the four screws and take off the cover plate from the back of thecontroller module (Figure 39).

3. What do you want to do?

v Remove only the power supply assembly from the chassis to servicethe DC power harnesses. Go to the next step.

v Remove only the controller card cage from the chassis to service thecontroller backpanel or battery harness. Go to Step 6 on page 84.

v Remove all of the parts from the chassis. Perform all of the remainingsteps in this procedure. Go to Step 4.

4. Remove the eight screws (four on each side) from the rearward sides of thechassis (Figure 40 on page 84).

5. Disconnect the harnesses (Steps 1 and 2 in Figure 40 on page 84).

Figure 39. Removing and Replacing the Cover Plate


Grasp the top, back edge of the power supply assembly and pull it backward afew inches (away from the connector plate). When you have enough room toput your hand behind power supply assembly, unplug all three DC powerharnesses.

6. Disconnect the DC power harnesses (Figure 41 on page 85).

Unplug the three DC power harnesses from the connector plate on the back ofthe controller module. There are two +5 Volt harnesses and one +12 Voltharness. If you are servicing the DC power harnesses, return to “Replacing theDC Power Harnesses” on page 128. Otherwise, go to the next step.

7. Unplug the battery harness (Figure 41 on page 85).

Unlock and disconnect the battery harness from the back of the controllermodule. Close the latches on the battery harness connector and lay theharness flat across the bottom of the access hole in the connector plate.

8. Remove the eight screws (four on each side) from the forward sides of thechassis (Figure 42 on page 85).

Figure 40. Removing Screws, Harnesses, and Power Supply Assembly


9. Lift the controller card cage assembly out of the chassis (Figure 42).

Grasp and lift the top, front edge of the controller card cage slightly (about oneinch). Pull the card cage firmly toward the front until the connectors on thecontroller backpanel exit the holes in the connector plate. Lift the controllercard cage out of the chassis and set it aside.

10. What do you want to do next?

v Reassemble the controller module. Go to the next step.

v Service the controller backpanel . Return to “Replacing a Failed ControllerBackpanel” on page 98.

Figure 41. DC Battery and Power Harness Connections

Figure 42. Removing the Controller Card Cage


v Service the battery harness . Return to “Replacing the Battery Harness” onpage 125 .

11. Reinstall the controller card cage in the chassis.

Reverse the sequence shown in Figure 42 on page 85 as you do the following:

a. Set the controller card cage into the chassis (backpanel toward connectorplate).

b. Grasp the top, front edge of the card cage and push the assembly until thebackpanel rests firmly against the connector plate. As you slide the cardcage backward, flatten battery harness against the bottom of the chassis tokeep the harness from being pinched between the controller card cage andconnector plate.

Note: There are four holes in the bottom frame of the controller card cage thatfit over four mounting pins in the top of the battery retainer shelf(Figure 42 on page 85). When you slide the controller card cage intoplace, you will feel it drop as the pins slip into these holes.

12. Secure the controller card cage with eight mounting screws (Figure 42 onpage 85).

13. Plug in the battery and power harnesses (Figure 41 on page 85).

14. Slide the power supply assembly into place (Figure 40 on page 84).

Slide the assembly forward until you can reconnect the DC power harnesses.Plug in both harnesses, then push the power supply assembly into its finalposition.

15. Secure the power supply assembly with eight mounting screws (Figure 40 onpage 84).

16. Replace the controller module chassis into the cabinet.

Reinstall the controller module in the cabinet by reversing the process that youused in Step 1 on page 83 of this procedure. Make sure that you:

v Tighten the mounting screws as necessary.

v Replace all the FRUs and lock them in place. Insert both controllers in theirproper slots (A or B).

v Reconnect all interface cables and power cords.

17. Turn on the power and check for faults.

Turn on both power switches on the back of the controller module and maincircuit breakers. Check the LEDs on the front and back of the controllermodule. All Power LEDs should be on and Fault LEDs should be off. If there isa problem, refer to the “Troubleshooting Quick Reference” on page 133.

18. Replace the front cover on the controller module.

End of Procedure


Chapter 4. Controllers

Overview

General Description

The controller module supports Redundant Array of Independent Disks (RAID)technology through its interface boards. There are two types of interface boards:

v Array controllers (Figure 43)

v Controller backpanel (not shown)

This chapter discusses how to identify interface problems and how to service thecontrollers. For detailed information on the controller backpanel, refer to “ControllerBackpanel” on page 96.

Identifying Interface Problems

Types of Interface Problems

Interface problems include any malfunctions that delay, interrupt, or preventsuccessful input/output (I/O) activity between the hosts and other devices on theFibre Channel network. This includes transmissions between the controller moduleand drive modules attached to it. For the purpose of this discussion, the controllermodule’s interface components include:

v Internal components

– Two Fibre Channel controllers

– Controller card cage (includes controller backpanel)

v External connections:

– Fibre Channel host adapters, cables, terminators, and hub or switchingdevices

– SCSI drive cables

Figure 43. Controller FRUs in Controller Module


Interface problems on any computer system can be divided into two maincategories:

v Software-related problems that hamper communications typically involve one ormore of the following elements:

– Host operating system software error

– Disk array or other application error

– Incorrect configuration settings

v Hardware-related problems that might disrupt communications include thefollowing elements:

– Loose, disconnected, damaged interface cables or connectors

– Improper SCSI termination on drive bus or defective terminators

– Improper interface ID settings (hardware switches)

– Failed controllers, memory modules, or controller backpanel

– Failed drive modules, host adapter boards, or other devices on the FibreChannel network

Hints for Troubleshooting Interface Problems

The first step is to determine whether the interface problem is caused by hardwareor software. Hardware problems indicate defective equipment. Software problemsindicate operating system or disk array application errors. The easiest way to dothis is to try the following:

v If the interface problem occurred during or immediately following a softwareactivity, try to undo whatever the software did, then step through each softwarefunction (in smaller increments) until the problem occurs again. This will identifythe function that is working incorrectly.

v If the interface problem occurred without an apparent software-related activity,check the operating system and storage management software for errormessages and associated procedures. This may help determine if it is a softwareor hardware problem. Check the operating system User’s Guide and the platformspecific Fibre Channel Storage Manager software User’s Guide for details onchecking error messages and error logs.

v Check the controller module for faults (see “Using the Status LEDs” on page 75and Table 18 on page 90). If any amber LEDs are on, go to the “TroubleshootingQuick Reference” on page 133 for instructions.

v Check all the interface cables, particularly the host Fibre Channel cables, tomake sure that they are securely connected and undamaged.

v If you moved the controller module to another location or attached new devicesto it, check the following:

1. Host ID settings for both controllers. Make sure these settings are unique(do not conflict with other devices). Change the settings as necessary.

2. SCSI ID settings on all attached drive modules. Make sure the Tray IDand Bridge Disable option bit are both set correctly. See Step 5 of “Installingthe Drive Module” on page 49 for more information. Change the settings asnecessary.

3. Interface cable connections. Make sure that all cables are routed correctly.Change the cable connections as necessary. See “LVD-SCSI Drive CableRouting Examples” on page 59 for information regarding interface cablerouting and connections to the controller module. (For cable connectioninformation for other devices, refer to applicable hardware manuals.)


v If you were sent here from the “AIX Error Codes (SRNs)” on page 15, then returnto the entry that sent you here. Otherwise, continue below.

Problems resulting from a defective host adapter board, controller, memory module,or controller backpanel may be difficult to detect. If checking all the items listedabove does not identify the problem, try:

1. Replacing the host adapter and appropriate interface cable to each host.

2. Replacing the controller FRU following the procedure in “Replacing a FailedController” on page 93.

3. Replacing the controller backpanel (controller card cage) following theprocedure in “Replacing a Failed Controller Backpanel” on page 98.

Controller FRU

Controller Description

Each controller comes in a removable, portable canister, called a controller FRU(Figure 44). The controller FRUs slide into one of two controller slots on the front ofthe controller module and plug directly into the controller backpanel (see “ControllerBackpanel Description” on page 96). Two handles lock the controller in place. Eachcontroller slot has a controller slot letter that identifies the physical location of thecontrollers in the chassis: controller slot A or controller slot B (Figure 45 onpage 90). There are ten LEDs on each controller (one power, one Fault, and eightStatus).

The controller module supports two controllers that attach to hosts via FibreChannel connections. The controllers also support a SCSI interface for attaching todrive modules. Each controller must have a unique host Fibre ID number assignedthrough ID switches on the back of the controller module or host software. For moreinformation on setting host IDs, refer to “Connectors and Host IDs” on page 41.

Figure 44. Controller FRU, Slots and LEDs

Chapter 4. Controllers 89

See Table 18 for Status LED information.

Table 18. Controller FRU Status LEDs Descriptions

Power:

Green LED indicates that the power is on

Normal Status: On

Problem Status: Off

Fault:

Amber LED indicates a controller fault

Normal Status: Off

Problem Status: On

Heartbeat:

(first status LED)

Green LED indicates that the controller is working

Normal Status: On¹(blinking)

Problem Status: On

Status:

(8 LEDs includingHeartbeat)

Green LEDs indicate individual status errors

Normal Status: F0000000 or F1101110¹

Problem Status: any other pattern (except during initialization)¹

¹ There are eight Status LEDs; the Heartbeat and seven others. The number and pattern ofgreen status LEDs that are in the ″ON″ state depends on how your system is configured (F =flashing):

v F 0 0 0 0 0 0 0 – indicates the controller is ACTIVE

v F 1 1 0 1 1 1 0 – indicates the controller is PASSIVE

v F 1 1 1 1 1 1 1 – indicates the controller is being held in reset (failed)

v any other pattern - indicates a controller problem except during initialization. The statusLEDs will flash various patterns during initialization (power on or reset) while the controllerperforms its self test diagnostics.

Note: The switch located to the immediate right of the Status LEDs is a controllerReset switch. DO NOT use this switch, unless directed to do so by your nextlevel of support.

Figure 45. Controller FRU, Slots and LEDs – cont.


Controller SpecificationsTable 19. Controller FRU Specifications

Category Criteria Specification

Weight Component weight 3.0 kg (6.6 lb)

Shipping weight 5.0 kg (11.0 lb)

Power Requirement +5 VDC 7.0 A

+12 VDC 0.1 A

Memory Processor/Cache Size 32/128 MB, 32/256 MB

Interface Hostv Fibre Channel

v Copper or fiber optic

v 1 host connection per controller

Drive v LVD SCSI

v 16-bit, Ultra-2 synchronous, differential

v 6 drive channels total

Diagnostic v 1 RS-232 connection per controller

v 1 Ethernet connection per controller

Array Support Drives channels 6

Drives per channel 10

Maximum no. of drives 60

RAID levels 0, 1, 3, and 5

Factory Settings Host ID v Controller A: ID 5

v Controller B: ID 4

Data Transfer Rates Fibre Channel Host 100 MB/sec maximum

LVD SCSI Drive 80 MB/sec (16-bit synchronous)

Controller Servicing Notes

Here are a few suggestions to consider when servicing the controllers in thecontroller module:

v Always use proper precautions against electrostatic discharge beforeremoving and handling the controller FRUs or other components inside thecontroller module.

v Always read pertinent documentation. This includes software instructions onreplacing failed interface components (controllers, memory, backpanels, etcetera)and documentation that may be shipped with the replacement controller FRU,particularly the kit instructions. Kit instructions often contain the most currentinformation regarding controller servicing.

v You can hot swap a failed controller (replace it while the controller module isturned on and operating) as long as the failed controller:

– Is one of a redundant pair, two controllers attached to the same host, and

– Has a “reset” or “failed” status in the storage management software or cannotbe accessed reliably by the host. In some cases, the host may not be able toaccess the controller reliably and will not be able to fail the controller. If thecontroller is not in the ″reset″ or ″failed″ state and your attempt to fail thecontroller from the host is unsuccessful, you should still continue with the


controller replacement. Attention: You should not remove a controller cardthat is in the active state unless the host is unable to force the controller intoa ″reset″ or ″failed″ state.

v If cache mirroring is enabled in a redundant pair of controllers and onecontroller fails , the second controller will assume processing functions withoutdata loss. However, some or all of the data may be lost if:

1. A catastrophic controller failure occurs in a non-redundant controller, or

2. Cache mirroring is disabled and a failure occurs before data can be writtenfrom cache memory to disk.

v Remove the front cover (Figure 30 on page 72) to service the controllers orview the LEDs on each FRU.

v Make sure that the new controller is the same type (memory size, forexample) as the one you are replacing.

v Status and error messages may be logged during controller replacement asthe host continues to poll for the controller.

Troubleshooting Controller Problems

Symptom: Controller LED (front cover) is on.

1. Possible Cause: Controller FRU missing or unplugged.

a. Check the Power LEDs on both controller FRUs. If both Power LEDs are on,go to Possible Cause 2. If one Power LED is off, make sure that the FRU isplugged in correctly and its handles are locked in place.

b. If the Power LED remains off or the Fault LED turns on, go to PossibleCause 2.

2. Possible Cause: Controller FRU failed.

a. Check the Fan LED on the front cover. If it is on, go to “TroubleshootingController Fan Problems” on page 105. If not, continue at the next step.

b. Replace the failed controller FRU using the instructions on “Replacing aFailed Controller” on page 93.

c. If the Fault LED remains on after replacing the controller, go to PossibleCause 3.

3. Possible Cause: Controller backpanel failed.

a. Replace the controller backpanel using the instructions in “Replacing aFailed Controller Backpanel” on page 98. If the Fault LED remains on afterreplacing the backpanel, call your next level of support.

Symptom: Software issued a controller error message.




Symptom: Controller and Fan LED (front cover) are on.

1. Possible Cause: Controller fan failure caused one or both controllers tooverheat.

a. Stop all activity to the controller module and turn off the power.


b. Replace the failed controller fan FRU using the instructions in “Replacing aFailed Controller Fan” on page 106.

c. Allow the controller module to cool down, then turn on the power.

d. Check both controller FRUs for fault LEDs. If a controller Fault LED turnson, replace the failed controller FRU using the instructions in “Replacing aFailed Controller”.

Replacing a Failed Controller

Tools and Equipment

Replacement controller FRU and grounding strap (or other antistatic protectiondevice)

Instructions

Use this procedure to replace a failed controller FRU.

1. Look at the LEDs on the front cover and answer the following questions(Figure 46).

v Is the amber Controller LED glowing on the front cover (second light frombottom)?

Yes: Go to Step 2 on page 94.

No: If the power supply or fan LED is lit on the front cover, go to“Troubleshooting Quick Reference” on page 133 for instructions. Otherwise,go to the next question.

v Has the operating system or storage management software issued an errorrelating to transmissions between the controller and hosts or drive modules?

Yes. Go to Step 2 on page 94.

No. Answer the next question.

v Can you perform I/O operations to the drives successfully?

Yes. Return to normal operation.

No. To help you determine the source of the problem, read “IdentifyingInterface Problems” on page 87. If you still cannot identify the problem, go toStep 2 on page 94 and replace the controller FRU.

Figure 46. LEDs on Front Covers


2. Read “Controller Servicing Notes” on page 91, then go to Step 3.

3. Remove the front cover (Figure 31 on page 73), check the controller FRU LEDs(Figure 45 on page 90), and answer the following questions.

v Is an amber Fault LED glowing on one of the controllers?

Yes: This indicates a failed controller. Note which controller has a fault (A orB).

No: This may indicate an overheating problem, a controller backpanel failureor a controller failure. If you’ve been directed to replace the controller FRU byanother procedure, diagnostics or the Recovery Guru, read the note below,then continue with Step 4. Otherwise, go to “Troubleshooting QuickReference” on page 133 for instructions.

Note: Electrostatic charges can damage sensitive components. Use agrounding wrist strap or other antistatic precaution before removing orhandling the controllers.

Removing a controller that is operating normally (not failed) couldresult in data loss. Normally, you should only remove a controller (a)that has a Fault LED glowing or (b) that you have marked as ″Failed″(off-line) or ″reset″ through the storage management software. If the hosthas not already marked the controller as ″Failed″ (off-line) or ″reset″,then you should attempt to fail the controller manually following theinstructions in the Fibre Channel Storage Manager User’s Guide for youroperating system:

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host,then refer to the section ″Manual Recovery/Controllers″ in the″Recovery″ chapter of the Fibre Channel Storage Manager andStorWatch Fibre Channel RAID Specialist, User’s Guide, SC26-7285.

v If the subsystem is attached to an AIX host, then refer to the″Replacing the Controller″ section in the ″Diagnostic Aids″ chapter ofthe Fibre Channel Storage Manager, Installation and User’s Guide forthe AIX Operating System, SC26-7290.

In some cases, the host may not be able to access the controller reliablyand will not be able to fail the controller. If your attempt to fail thecontroller from the host is unsuccessful, you should still continue with thiscontroller replacement procedure (step 4).

4. Remove the failed controller (Figure 47 on page 95).

5. Unpack and check the new controller FRU.

Using the proper handling precautions, remove the controller from the packingmaterial. Check the shipping invoice and the controller FRU to make sure thatthis is the same type of controller that you just removed (same firmware versionand memory size).


6. Install the new controller FRU (Figure 47).

7. Restore the controller’s operating status.

Note: Status and error messages may have been logged on the host during thecontroller replacement procedure because the host continues to poll forthe controller. If the Recovery Guru or diagnostics run without error andthere are no fault lights active after the replacement procedure, then youcan disregard these messages.

Use the storage management software to bring the controller back on-line, andto perform any necessary recovery procedures:

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel RAID Specialistsoftware, then follow the instructions in the Recovery Guru for returning thecontrollers to active/active status (using the Maintenance and Tuningapplication) and verifying the operating status (using the Recovery Guru).Refer to Fibre Channel Storage Manager and StorWatch Fibre Channel RAIDSpecialist, User’s Guide, SC26-7285.

v If the subsystem is attached to an AIX host, wait for 5 minutes and then runthe Advanced Diagnostics in System Verification mode from the diagnosticinterface (type ″diag″ from the command prompt), to return the controllers toactive/active mode and verify the operating status. The diagnostics mayreturn an error code if you run them immediately after replacing the controller.Refer to Fibre Channel Storage Manager, Installation and User’s Guide forthe AIX Operating System, SC26-7290 and Diagnostic Information for MultipleBus Systems, SA38-0509 (MAP 0410) for more information.

Check the LEDs on the controller FRU to make sure the Fault LED remains off.If the Fault LED remains on, it may indicate that the new controller has failed ora controller backpanel problem. Try replacing the controller with another one orrefer to the procedure for replacing the controller backpanel.

8. Replace the front cover on the controller module.

Figure 47. Removing and Installing a Controller FRU


End of Procedure

Controller Backpanel

Controller Backpanel Description

Both controller FRUs plug directly into a controller backpanel, which providesinterface and power connections between the components inside the chassis(controllers, power interface board, and fans), as well as to LVD-SCSI drives and todevices on the Fibre Channel network. Inside the chassis is the controller card cage(Figure 48), a modular structure consisting of controller slots and the controllerbackpanel.

Figure 48. Controller Card Cage


Controller Backpanel SpecificationsTable 20. Controller Backpanel Specifications


Power Connectors +5 VDC (2) 4-pin

+12 VDC (1) 14-pin

Battery (1) 50-pin card edge

Interface Connectors Fibre Channel host (2) 9-pin copper wire

SCSI drive (6) 68-pin, LVD, Ultra SCSI-2

Diagnostic (2) RS-232 and (2) Ethernet

Switches Fibre Host ID Seven switches per controller, IDs 0-127

Controller Backpanel Servicing Notes

If you need to replace the controller backpanel, you must replace the entirecontroller card cage, not just the board. Servicing the controller card cage is amajor task that requires you to remove and disassemble the chassis. Beforestarting the service procedure in “Replacing a Failed Controller Backpanel” onpage 98, make sure that you exhaust all other diagnostic possibilities, including:

v Checking and replacing any defective interface cables, terminators, and hostadapters (refer to “Hints for Troubleshooting Interface Problems” on page 88)

v Verifying that the controllers and memory modules are functioning properly (referto “Troubleshooting Controller Problems” on page 92)

v Verifying that the cooling system is working properly and that the controllers arenot overheated (refer to “Troubleshooting Controller Fan Problems” on page 105)

When replacing a defective controller backpanel, you must:

v Stop all bus processes and data transfers to the controller module and drives

v Make sure that cache memory is devoid of all data

v Turn off all power

v Remove the controller module from the cabinet

v Be sure the chassis is disassembled enough to remove the backpanel

Troubleshooting Controller Backpanel Problems

Symptom: Power LEDs (front and power supply FRUs) are on, but all other PowerLEDs are off.

1. Possible Cause: Other FRUs are missing or not installed correctly.

a. Check all FRUs in the controller module and make sure they are installedsecurely. If this does not fix the problem, go to Possible Cause 2.

2. Possible Cause: Defective DC power harness or power interface board.

a. Replace the DC power harnesses and the power supply assembly using theinstructions on “Replacing the DC Power Harnesses” on page 128 and“Replacing a Controller Module Chassis” on page 131. If this does not fix theproblem, go to Possible Cause 3.

3. Possible Cause: Failed controller backpanel.

a. Replace the controller card cage using the instructions in “Replacing aFailed Controller Backpanel” on page 98.


Symptom: Controller Fault LEDs (front cover and controller FRU) are on.

1. Possible Cause: Controller is missing or not installed correctly.

a. Check the Power LEDs on both controller FRUs. If one is off, make surethat the FRU is locked securely in place.

b. If the controller FRUs Power LED remains off, a FRU Fault LED turns on, orif both controller look normal yet the Controller LED on the front coverremains on, go to Possible Cause 2.

2. Possible Cause: Controller failure.

a. Replace the failed controller using the instructions on “Replacing a FailedController” on page 93. If this does not fix the problem, go to PossibleCause 3.


a. Replace the controller card cage using the instructions in “Replacing aFailed Controller Backpanel”.

Symptom: Software errors occur when attempting to access controllers or drives.

1. Possible Cause: Software function or configuration problems.

a. Check the appropriate software and documentation to make sure the systemis set up correctly or that the proper command was executed.

2. Possible Cause: Controller module power switches or main circuit breakers inrackmount cabinet turned off.

a. Make sure that all power switches are turned on.

3. Possible Cause: Loose, disconnected, or defective interface cables.

a. Check all the cables between the host, controller module, drive modules,and other devices on the network. Make sure they are undamaged(particularly fiber optic cables) and securely attached.

4. Possible Cause: Improper ID settings.

a. Make sure that the Fibre host IDs and SCSI drive IDs are set properly for alldevices, particularly if you just removed or added a new device to thenetwork.

5. Possible Cause: Failed controller or drive.

a. Check the controller module for a controller fault. If the Controller LED onthe front cover is turned on, replace the controller FRU using the instructionson “Replacing a Failed Controller” on page 93.

b. Check the drive module for a drive fault. If a failed drive is indicated, replacethe drive using the instructions in “Replace a Failed Drive” on page 160.


a. Replace the controller card cage using the instructions in “Replacing aFailed Controller Backpanel”.

Replacing a Failed Controller Backpanel

Attention: Electrostatic charges can damage sensitive components. Use agrounding wrist strap or other antistatic precautions before removing or handling thecomponents in the controller module.

Tools and Equipment

Replacement controller card cage, screwdrivers, and antistatic protection


Instructions

Use this procedure to replace a failed controller backpanel (controller card cage).

1. Have the customer stop all I/O, then power off the controller.

2. Remove all of the FRUs using the instructions in “Removing and InstallingFRUs” on page 79. When you are finished, continue at the next step in thisprocedure.

3. Remove the controller module from the cabinet.

To replace the controller backpanel, you must first remove the controllermodule’s chassis from the cabinet. See “Removing the Module from theRackmount Cabinet” on page 81. When you have the chassis out of thecabinet, set it on a dry, level surface (battery side down) and continue at thenext step.

4. Prepare and remove the controller card cage from the chassis.

Go to “Disassembling and Reassembling the Chassis” on page 83 and followthe instructions that apply to removing the controller card cage.

5. Unpack and install the new controller card cage (see Step 11 on page 86).

6. Reassemble the chassis by reversing the process you used in “Disassemblingand Reassembling the Chassis” on page 83.

7. Install the controller module into the cabinet.

Reverse the process you used in “Removing the Module from the RackmountCabinet” on page 81.

8. Install all the FRUs and reconnect all the cables (interface and power) byreversing the instructions in “Removing and Installing FRUs” on page 79.

9. Turn on the power and check the controller module.

Turn on both power switches on the back of the controller module and maincircuit breakers in the rackmount cabinet (if applicable). Check the front andback of the controller module to make sure that all green Power LEDs are onand all amber Fault LEDs are off. If any Fault LEDs turn on, go to“Troubleshooting Quick Reference” on page 133 for instructions. Use thestorage management software to check the overall status of the controllermodule.

10. Replace the front cover.

End of procedure


Chapter 5. Cooling System

Overview of Cooling System

General Description

The controller module’s cooling system (Figure 49) includes the followingcomponents:

v Controller fan FRU

v Power supply fan FRU

v Chassis ventilation holes

These components cool the controllers and power supplies by circulating airthrough the chassis. This chapter describes proper ventilation, the controller fanFRU and power supply fan FRU, and tells you how to service the cooling system.

Servicing the Cooling System

Cooling problems include any malfunctions or obstructions that impede air flow andcause one or more components in the controller module to overheat. To avoidcooling problems, always keep the air vents free of obstructions. Also, make surethat the ambient air temperature around the controller module is within theenvironmental requirements. (Refer to “Heating and Air Conditioning” on page 38).

Figure 49. Controller Module Cooling System


Preserving Proper Air Flow

The controller module must have proper air circulation throughout the chassis. Toboost air circulation, the chassis has air vents along its top and sides. These ventsserve as air intake and exhaust passages (Figure 50). Always keep vents clean andfree of obstructions.

Determining Which Fan Failed

Instructions

If the Fan LED on the front cover is glowing, it means that one of the fan FRUs inthe controller module has failed. Use this procedure to determine whether thecontroller fan or power supply fan has failed.

1. Check the LEDs on the front cover (Figure 51 on page 103).

If the Fan LED is on, look at the LEDs on the power supply fan FRU andchoose one of the following. If a different LED is glowing on the front cover, goto “Troubleshooting Quick Reference” on page 133.

v Power supply Fan FRU Fault LED is off . Go to “Replacing a FailedController Fan” on page 106.

v Power supply Fan FRU Fault LED is on . Go to “Replacing a Failed PowerSupply Fan” on page 109.

End of Procedure

Figure 50. Air Flow through Chassis


Controller Fan FRU

Controller Fan Description

The Controller Fan FRU (Figure 52 on page 104) is a single, removable unitcontaining two cooling fans, temperature monitoring logic, and five Status LEDs.See Table 21 for the LED status descriptions.

Table 21. Controller Fan FRU Status LEDs Descriptions

Power:


Normal Status: On

Problem Status: Off

Power Supply:

Amber LED indicates a power supply fault

Normal Status: Off

Problem Status: On

Fan:

Amber LED indicates a fan fault

Normal Status: Off

Problem Status: On

Controller:

Amber LED indicates a Controller fault

Normal Status: Off

Problem Status: On

Fast Write Cache:

Green LED turns on when data is in cache memory

Green LED turns off when data is written to disk

Normal Status: Blinking

Problem Status: Off

The dual fans provide a redundant cooling system to both controller FRUs. If onefan fails, the other will continue to operate, providing sufficient air circulation toprevent the controllers from overheating until you can replace the entire controllerfan FRU. The controller fan plugs directly into a slot on the front of the controllermodule, to the left of the controllers. It has a handle and captive screw for easyservice.

Figure 51. Controller Module Fan Fault LEDs

Chapter 5. Cooling System 103

Controller Fan SpecificationsTable 22. Controller Fan FRU Specifications


Weight Component Weight 0.9 kg (1.9 lb)

Shipping Weight 2.3 kg (5.0 lb)


+12 VDC 0.7 A

Figure 52. Controller Fan FRU and Status LEDs


Controller Fan Servicing Notes

You can hot swap the controller fan FRU (replace it while the controller module isturned on and running), as long as you complete the exchange within 15minutes . The time limit only applies to the total time that the fan FRU is out of thechassis. The time begins when you remove the failed FRU and ends when youre-seat the new one. This does not include the time it takes you to perform thisentire procedure (for example, checking LEDs).

Both fans failing simultaneously in the controller fan FRU is unlikely. Such a failurewould cause either one or both controllers to overheat. Under these circumstances,the amber controller LED on the front cover may turn on. Shut down the controllermodule immediately and let the unit cool to room temperature. Replace thecontroller fan (see “Replacing a Failed Controller Fan” on page 106) and turn on thepower. Check the controller fault LED. It should remain off. If not, replace thecontroller (see “Replacing a Failed Controller” on page 93).

Troubleshooting Controller Fan Problems

Symptom: Fan LED (front cover) is on or the host software reported a controllerfan problem.

1. Possible Cause: Power supply fan FRU is missing or unplugged.

a. Make sure the power supply fan FRU is plugged in correctly.

b. Check the LEDs on the power supply fan FRU. The power LED should beon and the Fault LED should be off. If so, go to Possible Cause 3. If thepower LED is off or the Fault LED is on, go to Possible Cause 2.

2. Possible Cause: Power supply fan FRU failed.

a. Replace the power supply fan FRU using the instructions on “Replacing aFailed Power Supply Fan” on page 109.

3. Possible Cause: Controller fan FRU is missing or unplugged.

a. Make sure controller fan FRU is plugged in correctly.

b. If Power LED remains off, it indicates a failed controller fan FRU. Go toPossible Cause 4.

4. Possible Cause: Controller fan FRU failed.

a. Check the Fault LED on power supply fan FRU. If the Fault LED is off,replace the controller fan FRU using the instructions on “Replacing a FailedController Fan” on page 106. If the Fault LED is on, replace the powersupply fan FRU using the instructions on “Replacing a Failed Power SupplyFan” on page 109.

5. Possible Cause: Circuitry failed or Power LED burned out on controller fan FRU.

a. Replace the controller fan FRU using the instructions on “Replacing a FailedController Fan” on page 106.

Symptom: Controller and Fan Fault LEDs (front cover) are on.

1. Possible Cause: Both a controller and the controller fan failed.

a. Check both controller FRUs for fault LEDs, then replace the failed controllerFRU using the instructions on “Replacing a Failed Controller” on page 93.

b. After replacing the failed controller, check the LEDs on the front cover. If theFan LED is still on, replace the controller fan FRU using the instructions on“Replacing a Failed Controller Fan” on page 106.




b. Replace the controller fan FRU using the instructions on “Replacing a FailedController Fan” below.


d. Check both controller FRUs for fault LEDs. If either Fault LED is on, replacethe controller fan FRU using the instructions on “Replacing a FailedController” on page 93.

Replacing a Failed Controller Fan

Tools and Equipment

Replacement controller fan FRU and screwdriver (optional).

Instructions

Use this procedure to replace a failed controller fan. The instructions assume thatyou used the procedure “Determining Which Fan Failed” on page 102 to identifythat the controller fan has failed.

1. Read “Controller Fan Servicing Notes” on page 105.

2. Unpack the new controller fan. Attention: Do not operate the controller modulewithout adequate ventilation and cooling to the controllers. Operating thecontroller module without proper cooling to the controllers may damage theircircuitry. You must shut down the controller module to avoid overheating if youtake more that 15 minutes to remove the controller fan FRU and insert the newone.

3. Remove the failed controller fan FRU (Figure 53 on page 107).

Remove the front cover from the controller module. Loosen the captive screwon the controller fan FRU by turning it counterclockwise. If the thumbscrew istoo tight, use a flat blade screwdriver to loosen it.

4. Install the new controller fan FRU (Figure 53 on page 107).

Slide the new FRU into the slot and tighten the screw. The captive screw isspring-loaded and will not tighten unless the fan FRU is inserted all the way intothe chassis. If the screw keeps spinning without tightening, push on the front ofthe fan FRU until it snaps into place-then tighten the captive screw.


5. Check the LEDs on the controller fan FRU (Figure 32 on page 76).

The green Power LED should be on and the amber LEDs should be off. If theFan LED turns on or the Power LED remains off, make sure that the controllerfan FRU is inserted all the way into the chassis and the thumbscrew is tight. Ifthe Fan LED remains on, it may indicate a problem with the new controller fanFRU. Replace the controller fan FRU with a spare one, if available. If not, turnoff the controller module until you get a replacement fan. This will prevent thecontrollers from overheating.


End of Procedure

Power Supply Fan FRU

Power Supply Fan Description

Like the controller fan, the power supply fan FRU (Figure 54 on page 108) is asingle, removable unit that contains two cooling fans. The dual fans provide aredundant cooling system to both power supply FRUs. If one fan fails, the other willcontinue to operate. A single fan will provide sufficient air circulation to prevent thepower supplies from overheating until you can replace the entire power supply fanFRU. The power supply fan FRU plugs directly into a slot on the back of thecontroller module, between the power supplies. It has a locking lever by which youunlatch and remove the power supply fan FRU.

Figure 53. Removing and Installing a Controller Fan


See Table 23 for the LED status descriptions.

Table 23. Power Supply Fan FRU Status LEDs Descriptions

Power:


Normal Status: On

Problem Status: Off

Fault:

Amber LED indicates a fan fault

Normal Status: Off

Problem Status: On

Power Supply FanTable 24. Power Supply Fan FRU Specifications





+12 VDC 0.65 A

Figure 54. Power Supply Fan FRU


Power Supply Fan Servicing Notes

You can hot swap the power supply fan FRU (replace it while the controller moduleis turned on and running), as long as you complete the exchange within 15minutes . This time limit applies only to the total time that the fan FRU is out of thechassis, beginning when you remove the failed unit and ending when you re-seatthe new one. This does not include the time it takes you to perform this entireprocedure (such as checking LEDs).

Both fans in the power supply fan FRU failing simultaneously is unlikely. Such afailure would cause one or both power supplies to overheat. Under thesecircumstances, the amber power supply LED on the front cover turns on and theoverheated power supply automatically shuts down (its green power LED turns off).Once the ambient air temperature cools to below 70° C (158° F), the power supplyautomatically turns on. Replace the failed power supply fan using the instructionson “Replacing a Failed Power Supply Fan”, then check the power supply LEDs(fault LED on the front and power LED on the back). If the power supply fault LEDremains on, replace the power supply fan using the instructions on “Replacing aFailed Power Supply Fan”.

Troubleshooting Power Supply Fan Problems

Symptom: Fan LED (front cover) is on or the host software reported a controllerfan problem.

1. Possible Cause: Power supply fan FRU missing or unplugged.

a. Make sure power supply fan FRU is plugged in correctly.

b. Check LEDs on power supply fan FRU. The power LED should be on andthe Fault LED should be off. If so, replace the controller fan FRU using theinstructions on “Replacing a Failed Controller Fan” on page 106. If the powerLED is off or the Fault LED is on, replace the power supply fan FRU usingthe instructions on “Replacing a Failed Power Supply Fan”.

Replacing a Failed Power Supply Fan

Tools and Equipment

Replacement power supply fan FRU

Instructions

Use this procedure to replace a failed power supply fan FRU. These instructionsassume that you used the procedure “Determining Which Fan Failed” on page 102to identify that the power supply fan has failed.

1. Read “Power Supply Fan Servicing Notes”.

2. Unpack the new power supply fan FRU.

3. Remove the power supply fan FRU (Figure 55 on page 110).


4. Install the new power supply fan FRU (Figure 55).

The lever will snap down when the FRU is seated properly in the chassis. If thelever remains up, push on the power supply fan FRU until it snaps into place.

5. Check the LEDs (Figure 33 on page 78).

The green power LED should be on and the amber fault LEDs should be off. Ifthe power LED remains off or the fault LED turns on, make sure that the powersupply fan FRU is inserted all the way into the chassis and locked in place.

If this does not correct the problem (the fault LED remains on), it may indicatethat the new fan FRU is malfunctioning. Replace the power supply fan FRU withanother FRU. If a spare power supply fan FRU is not available, turn off thecontroller module. This will prevent the power supplies from overheating whileyou get a replacement fan.

6. Replace the back cover.

End of Procedure

Figure 55. Removing and Installing a Power Supply Fan FRU


Chapter 6. Power System

Overview of Power System

General Description

The controller module’s power system includes the following components:

v One battery FRU

v Two power supply FRUs

v Two power cords (one for each power supply)

v Three internal power harnesses

v Power supply assembly (includes power interface board)

These components provide power to the controllers and fans inside the chassis.This chapter describes the basic features of the battery, power supplies, powerharnesses and power supply housing. In addition, it explains how to service thesecomponents.

Servicing the Power System

Power system problems include any malfunctions that delay or interrupt powerdistribution to the controller module and its components. This includes both externaland internal power problems such as power outages, weak batteries, or a failure ofthe power interface board. All power system failures are caused by some type of

Figure 56. Controller Module Power System FRUs


hardware problem, either in the incoming power lines, the building’s wiring, thecabinet’s electrical system, or in the controller module’s circuitry.

The batteries inside the battery FRU have a two-year life expectancy. Because thebattery FRU is a sealed unit, you must replace the entire FRU every two years (notjust the batteries) in order to keep the battery backup system in working order.

Types of Power System Problems

Some electrical problems are difficult to trace, especially if it involves complex sitewiring in a large facility. However, you can use the controller module’s LEDs and afew simple procedures in this chapter to determine if the power problem is in thecontroller module, the cabinet, or the building. For more information ontroubleshooting the controller module, refer to “Troubleshooting Quick Reference” onpage 133.

Hardware-Related Problems

Problems involving the hardware components in the controller module’s powersystem could include:

v Loose or damaged power connectors

v Disconnected or damaged power cables

v Weak or failed batteries

v Failed power supplies

v Failure of other power-related components of the controller module

v Power failure of the power unit (internal AC distribution unit or UPS)

v Power failure of the external AC source (building circuit breakers, wiring, or UPS)

Battery FRU

Battery Description

The controller module contains a portable, removable unit, called a battery FRU,that houses rechargeable batteries and a battery charger board. The battery FRUplugs into the front of the controller module (Figure 57 on page 113) where itprovides backup power to the controllers’ cache memory. During a power outage, aproperly charged battery FRU maintains electrical current to the controllers for up tothree days. Thus, all data stored in memory will be preserved as long as thebatteries can sustain power to the cache memory.


Battery SpecificationsTable 25. Battery FRU Specifications





+12 VDC 2.5 A

Battery Servicing Notes

Replace the battery every two years or whenever it fails to hold a charge. Theservice label on the battery FRU provides a blank line for recording the last date inwhich the battery was serviced. You can check the date on this label to determinewhen the FRU should be replaced. If you replace the battery FRU and stillexperience battery-related problems (such as a loss of battery power to thecontrollers or batteries not charging properly), the controller module may have adefective battery harness, battery connection on the controller backpanel, powerharnesses, or power interface board. Under these circumstances, try replacing thebattery harness first.

Attention: This product contains a SEALED LEAD ACID BATTERY. When thebattery assembly is replaced, the used battery assembly must be returned to IBMfor proper disposal.

Figure 57. Battery FRU

Chapter 6. Power System 113

Attention: The battery FRU is a sealed canister. There are no user-serviceableparts inside. When servicing the battery FRU, replace the entire FRU, not individualbatteries or parts. Opening the battery FRU will void your warranty.

Troubleshooting Battery Problems

Symptom: Fault-A or Fault-B LED (battery FRU) is on.

1. Possible Cause: Left or right battery bank has failed.

a. Replace the battery FRU using the instructions on “Replacing the BatteryFRU” on page 116.

Symptom: Full Charge-A or Full-Charge-B LED (battery FRU) is off.

1. Possible Cause: Left or right battery bank is not yet fully charged.

a. Turn on the power and allow controller module to run 24 hours in orderrecharge the battery.

b. If after 24 hours, the Full Charge LED remains off or one of the Fault LEDsturns on, replace the battery FRU using the instructions on “Replacing theBattery FRU” on page 116.

Symptom: “Battery Low” error issued by software.

1. Possible Cause: Power turned off for extended period and drained batterypower.

a. Turn on the power and allow controller module to run 24 hours to rechargethe batteries.

b. If after 24 hours, the battery low error persists, replace the battery FRUusing the instructions on “Replacing the Battery FRU” on page 116.

2. Possible Cause: Batteries are weak and FRU is due for replacement.

a. Check the last service date for the battery FRU. If it has been two yearssince the battery was replaced, replace the battery FRU using theinstructions on “Replacing the Battery FRU” on page 116.

Symptom: Battery FRU is new, but will not hold a charge.

1. Possible Cause: Battery charger board failure.


b. Allow the system to run for at least 24 hours in order to properly charge thebatteries. If this does not solve the problem, go to Possible Cause 2.

2. Possible Cause: Faulty battery harness

a. Replace both power supplies using the instructions on “Replacing a FailedPower Supply” on page 122

b. Replace the battery harness using the instructions on “Replacing the BatteryHarness” on page 125.

Symptom: Loss of battery backup during a power outage.

1. Possible Cause: Battery failure or battery FRU is missing.



Checking the Battery Service Date

Note: Under normal circumstances, replace the battery FRU every two years.Using the controller module in a hot environment (above 35° C or 95° F),lowers the life expectancy of the battery FRU. Under these conditions youmay need to replace the battery every six months.

Instructions

Use this procedure to check the service date on the battery FRU. For moreinformation about the battery, refer to “Battery Description” on page 112.

1. Remove the front cover from the controller module (Figure 58).

2. Check the “Date of Installation” on the label (Figure 59 on page 116).

The battery should be replaced within two years of the installation date. If it istime to replace the battery, install a new battery FRU using the instructions in“Replacing the Battery FRU” on page 116. Otherwise, go to the next step.

3. Replace the front cover on the controller module (Figure 58).

Note: The battery date can also be verified using the RAID Manager for DOS.See “Chapter 16. RAID Manager for DOS” on page 205. Use theprocedure in “Display and Set the Battery Age” on page 226 to view thebattery age.

End of Procedure

Figure 58. Removing and Replacing a Front Cover


Replacing the Battery FRU

The battery FRU should be replaced every two years as part of routine preventivemaintenance.

Tools and Equipment

Replacement battery FRU and flat blade screwdriver (optional)

Instructions

Use this procedure to replace the battery FRU as part of routine maintenance.

1. Unpack the battery FRU. Save the shipping material for returning the usedbattery FRU to IBM for disposal. (Figure 57 on page 113).

v Record today’s date on the blank line next to “Date of Installation.”

v Record the expiration date (two years from today’s date) on the blank linenext to “Replacement Date.”

2. Remove the front cover from the controller module (Figure 58 on page 115).

3. Remove the battery FRU (Figure 60 on page 117).

Figure 59. Battery FRU Service Label


Turn the captive screws on the battery FRU counterclockwise. If they are tootight, use a flat blade screwdriver to loosen the screws.

4. Install the new battery (Figure 60).

Slide the battery FRU into the slot and tighten all captive screws.


6. Reset the battery timer.

If the subsystem is attached to a Windows NT, SUN, or HP-UX host systemrunning the Fibre Channel Storage Manager software or a Windows NT orWindows 95 system running the StorWatch Fibre Channel Specialist software,then use the raidutil utility from the command prompt on the host system toreset the battery timer on each controller (raidutil -c controller_name -R ). Thecommand must be issued from the directory containing the Fibre ChannelStorage Manager executable files and must be issued for each controller. Youcan determine the name of the controllers by selecting the Locate Module iconfrom any Fibre Channel Storage Manager application or by issuing the ladcommand from the command prompt. For example:c:\Program Files\IBM\fcsm> ladDrive0 1T80402577 LUNS: 0Drive8 1T81207809 LUNS: 1

c:\Program Files\IBM\fcsm> raidutil -c Drive0 -RLUNs found on Drive0LUN 0 RAID 5 333 MBraidutil succeeded!

c:\Program Files\IBM\fcsm> raidutil -c Drive8 -R

Figure 60. Removing and Installing the Battery FRU


LUNs found on Drive8LUN 1 RAID 5 200 MB

raidutil succeeded!

Consult the Fibre Channel Storage Manager documentation for more details onusing the raidutil and lad commands.

If the subsystem is attached to an AIX host system, or you do not have accessto the command line utility described above, then you must reset the batterytimer using RAID Manager for DOS (DRM). You will have to connect the serviceterminal to each controller in turn and select the Maintenance → Reset theBattery Timer option from the main menu. See “Display and Set the BatteryAge” on page 226 for more information.

7. Allow the system to run for at least 24 hours in order to properly charge thebatteries.

When properly charged, both Full Charge LEDs will be glowing on the front ofthe battery FRU.

8. Using the original shipping material, return the used battery FRU to IBM forproper disposal.

Attention: This product contains a SEALED LEAD ACID BATTERY. When thebattery assembly is replaced, the used battery assembly must be returned to IBMfor proper disposal.

End of Procedure

Power Supply FRU

Power Supply Description

Two power supplies in the controller module provide electrical power to the internalcomponents by converting incoming AC voltage to DC voltage. Both power suppliesare housed in removable power supply FRUs. The FRUs slide into either of the twoslots on the back of the controller module (Figure 61 on page 119) and plug directlyinto the power interface board. See “Power Interface Board Description” onpage 130.

Each power supply uses one power cord. You can plug both power cords to acommon power source or plug each cord into a separate circuit (which will providepower source redundancy). The power supplies are interchangeable and redundant.This means that one power supply will maintain electrical power to the controllermodule if the second power supply is turned off or malfunctions. In addition,redundant power supplies support hot swapping, a feature that allows you toreplace a failed power supply while the controller module is powered-up andrunning.


Table 26. Power Supply FRU Status LEDs Description

Power:

Green LED indicates that the power is on:

v Normal status, all power turned on: On

(LEDs on both power supplies are on; Power LED on front coveris on)

v Normal status, all power turned off or one power supply turnedoff: Off

(LED on one or both power supplies are off; Power LED on frontcover is off)

v Problem status, one power supply failure: Off

(LED on failed power supply is off; LEDs on other power supplyand front cover are On)

Power Supply SpecificationsTable 27. Power Supply FRU Specifications




Power Requirement +12 VDC 1.0 A (max. per FRU @ 220 v AC)

2.0 A (max. per FRU @ 110 v AC)

Power Supply Recovery Notes

Both power supplies have a built-in temperature sensor designed to prevent thepower supplies from overheating. If a temperature sensor detects anover-temperature condition (ambient air temperature of 70° C (158° F or above) the“overheated” power supply will automatically shut down. The other power supplyremains on as long as its temperature remains below 70° C (158° F). If not, thesecond power supply will shut down, which turns off all power to the controllermodule. There is a serious problem in the cabinet if the air temperature inside thecabinet is hot enough to cause the power supplies to shut down!

Figure 61. Power Supply FRU


Once the air temperature cools to below 70° C (158° F), the power suppliesautomatically restart. An automatic restart resets the controllers, attempts to spin upthe drives (which has no effect on the drives if they are already running), andreturns the controller module to a normal operating state. Typically, you will notneed to perform recovery procedures after an automatic power supply shutdownand restart.

Troubleshooting Power Supply Problems

Symptom: No power to the controller module (all Power LEDs off).

1. Possible Cause: Power switches turned off.

a. Turn on both power switches on the controller module

b. Turn on the main circuit breakers in the rackmount cabinet, if applicable.

2. Possible Cause: Power cords unplugged.

a. Check to make sure all power cords are plugged in securely.

3. Possible Cause: Rack power failure.

a. Go to the power MAP for the rack in Seascape Solution Rack, Installationand Service Guide, IBM 2101 Model 100, SY27-7606.

4. Possible Cause: Power supplies overheated or failed.

a. Wait 10 minutes. If the power supplies turn on automatically, use therecovery procedure on “Recovering from a Power Supply Shutdown” onpage 121. If not, go to step 4.b.

b. Go to “Replacing a Failed Power Supply” on page 122 and replace thepower supplies

Symptom: One power supply LED (FRU) is on and the other is off.

1. Possible Cause: Power supply is turned off or unplugged.

a. Plug in the power cord and turn on the power switch. If the LED remains off,go to Possible Cause 2.

2. Possible Cause: Power supply is overheated or failed.

a. Wait 10 minutes. If the power supply turns on automatically, use therecovery procedure on “Recovering from a Power Supply Shutdown” onpage 121. If not, go to step 2.b.

b. Replace the power supply FRU using the instructions on “Replacing a FailedPower Supply” on page 122.

Symptom: Power Supply LED (front cover) is on.

1. Possible Cause: Power supply is missing or not plugged in properly.

a. Insert and lock the power supply into place. If the fault LED is still on, go toPossible Cause 2.





Recovering from a Power Supply Shutdown

Instructions

Use this procedure to regain normal system operation after a power supplyshutdown. For more information on the power supplies, refer to “Power SupplyDescription” on page 118.

1. Read the information in “Power Supply Recovery Notes” on page 119

2. Answer the following questions:

Does the current problem match one of the conditions listed below?

v One power supply shut down. The Power LED on the FRU and the PowerSupply LED on the front cover are off.

v Both power supplies shut down. All power to the controller module is off,but the drives keep running without fault.

v Power supplies restart. One or both power supplies shut down, then turn onagain automatically.

v Temperature. The air temperature at the back of the controller module is 70°C [158° F] or higher.

Yes: Go to Step 3.

No: Go to the next question.

Are both power cords plugged in securely on the controller module andAC units in the cabinet or external AC outlet?

Yes: Go to the next question.

No: Correct the problem and continue normal operation.

Is the Power Supply LED glowing on the front cover?

Yes: This indicates a failed power supply. Go to “Replacing a Failed PowerSupply” on page 122.

No: Go to “Power Problems” on page 136. Attention: If the air temperatureinside the cabinet is hot enough to cause the power supplies to shutdown, 70°C (158° F) or above, there is a serious problem in the cabinet. Open the cabinetdoors immediately to help cool the controller module and drives. Then dowhatever is necessary to alleviate the over-temperature problem (such asshutting down the power or using external fans to cool the area).

3. Cool the area to a normal operating temperature, then check the powersupplies.

If the power LED on one or both power supplies turns on again, go to Step 4. Ifthe power supply (or both power supplies) remain off, it may indicate a faultypower cord, a failed power supply (see “Replacing a Failed Power Supply” onpage 122), or a failed power interface board (see “Replacing a ControllerModule Chassis” on page 131).

4. Check the system for faults or damage.

Once the power supplies turn on again, check all the LEDs on the controllermodule and the attached drive modules.


End of Procedure

Replacing a Failed Power Supply

Tools and Equipment

Replacement power supply FRU

Instructions

Use this procedure to replace a failed power supply.

1. Check the LEDs on the front and back of the controller module (Figure 62).

If a power supply has failed, the amber Power Supply LED on the front coverwill be turned on. Look on the back of the controller module. The green PowerLED on the failed power supply will be turned off.

2. Turn off the power switch and unplug the power cord from the failed powersupply (Figure 63 on page 123).CAUTION:

Energy hazard, remove power before servicing.

Always turn off the power switch and unplug the power cord before you removeor install a power supply FRU.

3. Remove the failed power supply (Figure 64 on page 123).

Figure 62. Fault Indicators for a Failed Power Supply


4. Unpack and install the new power supply (Figure 64).

5. Plug in the power cord and turn on the power (Figure 63).

6. Check the new power supply and other controller module LEDs for faults.

End of Procedure

Battery Harness

Battery Harness Description

The controller module contains one battery harness. The battery harness (Figure 65on page 124) is a ribbon cable that provides a power connection between the

Figure 63. Turning Off the Power and Unplugging the Power Cord

Figure 64. Removing and Installing a Power Supply FRU


battery FRU and the controller backpanel. The harness also carries battery statusinformation.

Battery Harness SpecificationsTable 28. Battery Harness Specifications


Size Length 10.5 in.

Connector To Battery FRU 34-pin ribbon

To Controller Backpanel 50-pin card edge

Power Transfer +5 VDC 0.07 A

+12 VDC 2.5 A

Battery Harness Servicing Notes

An intermittent or complete loss of battery power to the controllers or batteries notcharging properly may indicate a defective battery harness or controller backpanel.To replace a battery harness (or controller backpanel), you must remove thecontroller module from the cabinet and completely disassemble the chassis. For thisreason, you should try all other diagnostic and servicing procedures first, before youreplace these items. Specifically, make sure that you replace the battery FRU, bothpower supplies, and both power cords before you attempt to replace the batteryharness.

When replacing a defective battery harness, you must:





v Be sure the chassis is disassembled enough to allow the unplugging of theharness

Figure 65. Battery Harness


Troubleshooting Battery Harness Problems

Symptom: Battery FRU is new, but will not hold a charge.

1. Possible Cause: Battery harness defective.


b. Replace both power supplies using the instructions on “Replacing a FailedPower Supply” on page 122.

c. Allow the system to run for at least 24 hours in order to properly charge thebatteries. If this does not solve the problem, replace the battery harnessusing the instructions on “Replacing the Battery Harness”.

Replacing the Battery Harness

Attention: Only qualified, trained service technicians should perform thisprocedure. This procedure involves disassembling the controller module to replaceinternal components. Electrostatic discharge can damage sensitive components.Use a grounding wrist strap or other antistatic precautions before removing orhandling the components in the controller module.

Tools and Equipment

Replacement battery harness, screwdrivers, and antistatic protection

Instructions

Use this procedure to replace a defective battery harness. The following instructionsassume that you already replaced the battery FRU and both power supplies, but thebatteries are not charging properly.




To replace the battery harness, you must first remove the controller module’schassis from the cabinet; see “Removing the Module from the RackmountCabinet” on page 81. When you have the chassis out of the cabinet, set it on adry, level surface (battery side down) and continue at the next step.

4. Remove the controller card cage from the chassis.

Go to “Disassembling and Reassembling the Chassis” on page 83 and followthe portion of those instructions for removing the controller card cage from thechassis. During this process, you will disconnect the battery harness from theback of the controller module (Figure 66 on page 126). Once the controllercard cage is out, continue at the next step.

5. Disconnect the battery harness.

To locate the battery harness, look inside the chassis beneath the area fromwhich you just removed the controller card cage. To remove the batteryharness, loosen the two screws holding the harness in place and remove theharness from the chassis.


6. Unpack and install the new battery harness.

Secure the connector on the new battery harness to the mounting bracket withtwo screws. Route the harness from the mounting bracket to the rear accesshole (where you removed the old harness) and out through the slot in the rearshield. Make sure that the harness is flat against the bottom of the chassis.

7. Reinstall the controller card cage in the chassis (see “Disassembling andReassembling the Chassis” on page 83).

8. Install the controller module into the cabinet (see “Disassembling andReassembling the Chassis” on page 83).



Turn on both power switches on the back of the controller module and maincircuit breakers in the cabinet (if applicable). Check the front and back of thecontroller module to make sure that all green Power LEDs are glowing and allamber Fault LEDs are off. If any Fault LEDs turn on, go to“TroubleshootingQuick Reference” on page 133 for instructions. Use the storage managementsoftware to check the overall status of the controller module. If there is still aproblem with the battery system, replace the controller backpanel (see“Replacing a Failed Controller Backpanel” on page 98).

End of Procedure

DC Power Harnesses

DC Power Harness Description

The controller module contains three DC Power harness: two +5 VDC and one +12VDC. The power harnesses (Figure 67 on page 127) provide power connectionsbetween the power interface board and the controller backpanel.

Figure 66. Removing and Installing a Battery Harness


DC Power Harness SpecificationsTable 29. DC Power Harness Specifications


Connectors +5 VDC 4-pin male N-LOK on both ends

+12 VDC 14-pin male N-LOK on both ends

Power Transfer +5 VDC Up to 25 A

+12 VDC Up to 4 A

DC Power Harness Servicing Notes

An intermittent or complete power loss to the controllers, battery FRU, or controllerfan may indicate either a defective power harness or power interface board. Thisprocedure tells how to replace two DC power harnesses (+5 volt and +12 voltharnesses). If replacing the harnesses does not resolve the problem, you may needto replace the entire controller module chassis, which includes the power supplyhousing and the interface board. See “Replacing a Controller Module Chassis” onpage 131.

When replacing defective DC power harnesses, you must:





v Be sure the chassis is disassembled enough to allow the unplugging of theharnesses

Troubleshooting DC Power Harness Problems

Symptom: Power is turned on and working in the rackmount cabinet, but thecontroller module has no power.

Figure 67. DC Power Harnesses


1. Possible Cause: Controller module is unplugged or turned off.

a. Plug in both power cords and turn on both power switches (see “Identifyingthe Parts” on page 69). If this does not fix the problem, go to PossibleCause 2.

2. Possible Cause: Power supply failure.

a. Check the power supply LED on the front cover. If it is on, go to the nextstep. If not go to the next symptom.

b. Look at the LEDs on both power supply FRUs. If a Fault LED is on, replacethe failed power supply FRU using the instructions on “Replacing a FailedPower Supply” on page 122. If both are off, go to the next symptom.

Symptom: The LEDs on both power supply FRUs are on, but all other LEDs areoff.

1. Possible Cause: Defective DC power harness.

a. Replace the DC power harnesses using the instructions on “Replacing theDC Power Harnesses”.

Replacing the DC Power Harnesses

Attention: This procedure involves servicing sensitive components, which mayinvolve disassembling the controller module to replace internal harnesses.Electrostatic charges can damage sensitive components. Use a grounding wriststrap or other antistatic precautions before removing or handling the components inthe controller module.

Tools and Equipment

Replacement power harnesses (+5 volt and +12 volt), screwdrivers, and antistaticprotection

Instructions

Use this procedure to replace defective DC power harnesses. The followinginstructions assume that you already replaced both power supplies and are stillhaving power problems.




To replace the DC power harnesses, you must first remove the controllermodule’s chassis from the cabinet; see “Removing the Module from theRackmount Cabinet” on page 81. When you have the chassis out of the cabinet,set it on a dry, level surface (battery side down) and continue at the next step.

4. Unplug the harnesses.

Go to “Disassembling and Reassembling the Chassis” on page 83 and followthe instructions that explain how to disassemble the chassis far enough tounplug the DC power harnesses. Once you have unplugged all three harnesses,continue at the next step.


5. Unpack and install the new harnesses.

6. Reassemble the chassis by reversing the process you used in Step 4 onpage 128.

7. Install the controller module into the cabinet (reverse the process you used inStep 3 on page 128).



Turn on both power switches on the back of the controller module and maincircuit breakers in the cabinet (if applicable). Check the front and back of thecontroller module to make sure that all green Power LEDs are glowing and allamber Fault LEDs are off. If any Fault LEDs turn on, go to“TroubleshootingQuick Reference” on page 133 for instructions. Use the storage managementsoftware to check the overall status of the controller module. If there is still aproblem with the power system, replace the power interface board (see“Replacing a Controller Module Chassis” on page 131).

End of Procedure

Figure 68. Reconnecting the DC Power Harnesses


Power Interface Board

Power Interface Board Description

Both power supplies plug directly into a power interface board, which provideselectrical connections between the power supplies and other components in thechassis. The power interface board is an integral part of the Controller Modulechassis that also holds the Power Supply housing and the Backpanel.

Power Interface SpecificationsTable 30. Power Interface Specifications


Connectors +5 VDC 4-pin male N-LOK on both ends

+12 VDC 14-pin male N-LOK on both ends

Power Interface Board Servicing Notes

The power supply assembly is a part of the Controller Module chassis. If you needto replace the power interface board, you must replace the entire controller modulechassis. If there is an intermittent or complete power loss to the controllers, batteryFRU, or controller fan, it might be caused by either a defective power harness orpower interface board. The procedure in this section explains how to replace thecontroller module chassis, which includes the power interface board. It assumesthat you have already checked the power cords, checked for a failed power supply

Figure 69. Power Supply Assembly


(“Troubleshooting Power Supply Problems” on page 120), and replaced the powerharnesses (“Troubleshooting DC Power Harness Problems” on page 127).

When replacing a defective Power Interface Board, you must:





v Remove all the FRUs from the controller module chassis

Troubleshooting Power Interface Board Problems

Symptom: Power is turned on and working in the rackmount cabinet, but thecontroller module has no power.

1. Possible Cause: Controller module is unplugged or turned off.

a. Plug in both power cords and turn on both power switches. If this does notresolve the problem, go to Possible Cause 2.


a. See if the power supply fault LED on the front cover is on. If so, go to thenext step. If not go to the next symptom.

b. Look at the LEDs on both power supply FRUs. If a Fault LED is on, replacethe failed power supply using the instructions on “Replacing a Failed PowerSupply” on page 122. If both are off, go to the next symptom.

Symptom : The LEDs on both power supply FRUs are on, but all other LEDs areoff.

1. Possible Cause: Defective DC power harness.

a. Replace the DC power harnesses using the instructions on “Replacing theDC Power Harnesses” on page 128. If this does not resolve the problem, goto Possible Cause 2.

2. Possible Cause: Defective power interface board.

a. Replace the power interface board using the instructions on “Replacing aController Module Chassis”.

Replacing a Controller Module Chassis

Attention: This procedure involves removing all the controller FRUs from thecontroller module chassis and removing the controller module chassis from therack. Electrostatic charges can damage sensitive components. Use a groundingwrist strap or other antistatic precautions before removing or handling thecomponents in the controller module.

Tools and Equipment

Replacement controller module chassis, screwdrivers, and antistatic protection

Instructions

Use this procedure to replace a controller chassis, which includes the powerinterface board.




3. Remove the controller module from the cabinet using the instructions in“Removing the Module from the Rackmount Cabinet” on page 81. When youhave the chassis out of the cabinet, set it on a dry, level surface (battery sidedown) and continue at the next step.

4. Unpack and install the new power supply assembly.

5. Reassemble the chassis by reversing the process you used in “Disassemblingand Reassembling the Chassis” on page 83.

6. Install the controller module into the cabinet.

Reverse the process you used in“Removing the Module from the RackmountCabinet” on page 81.



Turn on both power switches on the back of the controller module and maincircuit breakers in the cabinet (if applicable). Check the front and back of thecontroller module to make sure that all green Power LEDs are glowing and allamber Fault LEDs are off. If any Fault LEDs turn on, go to“TroubleshootingQuick Reference” on page 133 for instructions. Use the storage managementsoftware to check the overall status of the controller module. If there is still aproblem with the power system, replace the controller backpanel (see“Replacing a Failed Controller Backpanel” on page 98).


End of Procedure


Chapter 7. Reference

Troubleshooting Quick Reference

Controller and Interface Problems

Symptom: Controller LED (front) is on.1. Possible Cause: Controller FRU missing or unplugged.

a. Check the Power LEDs on both controller FRUs. If both Power LEDs are on,go to Possible Cause 2. If one Power LED is off, make sure that the FRU isplugged in correctly and its handles are locked in place.

b. If the Power LED remains off or the Fault LED turns on, go to PossibleCause 2.




c. If the Fault LED remains on after replacing the controller, go to PossibleCause 3.

3. Possible Cause: Controller backpanel failed.

a. Replace the controller backpanel using the instructions on “Replacing aFailed Controller Backpanel” on page 98. If the Fault LED remains on afterreplacing the backpanel, call your next level of support.

Symptom: Software issued a controller error message.1. Possible Cause: Controller FRU failed.



Symptom: Controller and Fan LEDs (front) are on.1. Possible Cause: Controller fan failure caused one or both controllers to

overheat.


b. Replace the failed controller fan FRU using the instructions on “Replacing aFailed Controller Fan” on page 106.


d. Check both controller FRUs for fault LEDs. If a controller Fault LED turnson, then replace the failed controller FRU using the instructions on“Replacing a Failed Controller” on page 93.

Symptom: Power LEDs (front and power supply FRUs) are on,but all other Power LEDs are off.1. Possible Cause: Other FRUs are missing or not installed correctly.

a. Check all FRUs in the controller module and make sure they are installedsecurely. If this does not fix the problem, go to Possible Cause 2.


2. Possible Cause: Defective DC power harness or power interface board.

a. Replace the DC power harnesses and the power supply assembly using theinstructions on “Replacing the DC Power Harnesses” on page 128 and“Replacing a Controller Module Chassis” on page 131. If this does not fix theproblem, go to Possible Cause 3.


a. Replace the controller card cage using the instructions on “Replacing aFailed Controller Backpanel” on page 98.

Symptom: Controller Fault LEDs (front and controller FRU) areon.1. Possible Cause: Controller is missing or not installed correctly.

a. Check the Power LEDs on both controller FRUs. If one is off, make surethat the FRU is locked securely in place.

b. If the controller FRUs Power LED remains off, a FRU Fault LED turns on, orif both controller look normal yet the Controller LED on the front coverremains on, go to Possible Cause 2.

2. Possible Cause: Controller failure.

a. Replace the failed controller using the instructions on “Replacing a FailedController” on page 93. If this does not fix the problem, go to PossibleCause 3.



Symptom: Software errors occur when attempting to accesscontrollers or drives.1. Possible Cause: Software function or configuration problems.

a. Check the appropriate software and documentation to make sure the systemis set up correctly or that the proper command was executed.

2. Possible Cause: Controller module power switches or main circuit breakers inrackmount cabinet turned off.

a. Make sure that all power switches are turned on.

3. Possible Cause: Loose, disconnected, or defective interface cables.

a. Check all the cables between the host, controller module, drive modules,and other devices on the network. Make sure they are undamaged(particularly fiber optic cables) and securely attached.

4. Possible Cause: Improper ID settings.

a. Make sure that the Fibre host IDs and SCSI drive IDs are set properly for alldevices, particularly if you just removed or added a new device to thenetwork.

5. Possible Cause: Failed controller or drive.

a. Check the controller module for a controller fault. If the Controller LED onthe front cover is turned on, replace the controller FRU using the instructionson “Replacing a Failed Controller” on page 93.

b. Check the drive module for a drive fault. If a failed drive is indicated, replacethe drive using the instructions in “Replace a Failed Drive” on page 160.




Cooling Problems

Symptom: Fan LED (front) is on or the host software reported acontroller fan problem.1. Possible Cause: Power supply fan FRU is missing or unplugged.

a. Make sure the power supply fan FRU is plugged in correctly.

b. Check the LEDs on the power supply fan FRU. Power LED should be on,Fault LED should be off. If so, go to Possible Cause 3. If the power LED isoff or the Fault LED is on, go to Possible Cause 2.

2. Possible Cause: Power supply fan FRU failed.

a. Replace the power supply fan FRU using the instructions on “Replacing aFailed Power Supply Fan” on page 109.

3. Possible Cause: Controller fan FRU is missing or unplugged.

a. Make sure controller fan FRU is plugged in correctly.

b. If Power LED remains off, it indicates a failed controller fan FRU. Go toPossible Cause 4.

4. Possible Cause: Controller fan FRU failed.

a. Check the Fault LED on power supply fan FRU. If the Fault LED is off,replace the controller fan FRU using the instructions on “Replacing a FailedController Fan” on page 106. If the Fault LED is on, replace the powersupply fan FRU using the instructions on “Replacing a Failed Power SupplyFan” on page 109.

5. Possible Cause: Circuitry failed or Power LED burned out on controller fan FRU.

a. Replace the controller fan FRU using the instructions on “Replacing a FailedController Fan” on page 106.

Symptom: Controller and Fan LEDs (front) are on.1. Possible Cause: Both a controller and the controller fan failed.

a. Check both controller FRUs for fault LEDs, then replace the failed controllerFRU using the instructions on “Replacing a Failed Controller” on page 93.

b. After replacing the failed controller, check the LEDs on the front cover. If theFan LED is still on, replace the controller fan FRU using the instructions on“Replacing a Failed Controller Fan” on page 106.



b. Replace the controller fan FRU using the instructions on “Replacing a FailedController Fan” on page 106.


d. Check both controller FRUs for fault LEDs. If either Fault LED is on, replacethe controller fan FRU using the instructions on “Replacing a FailedController” on page 93.

Chapter 7. Reference 135

Power Problems

Symptom: Fault-A or Fault-B LED (battery FRU) is on.1. Possible Cause: Left or right battery bank has failed.


Symptom: Full Charge-A or Full-Charge-B LED (battery FRU) isoff.1. Possible Cause: Left or right battery bank is not yet fully charged.

a. Turn on the power and allow controller module to run 24 hours in orderrecharge the battery.

b. If after 24 hours, the Full Charge LED remains off or one of the Fault LEDsturns on, replace the battery FRU using the instructions on “Replacing theBattery FRU” on page 116.

Symptom: “Battery Low” error was issued by software.1. Possible Cause: Power turned off for extended period and drained battery

power.

a. Turn on the power and allow controller module to run 24 hours to rechargethe batteries.

b. If after 24 hours, the battery low error persists, replace the battery FRUusing the instructions on “Replacing the Battery FRU” on page 116.

2. Possible Cause: Batteries are weak and FRU is due for replacement.

a. Check the last service date for the battery FRU. If it has been two yearssince the battery was replaced, replace the battery FRU using theinstructions on “Replacing the Battery FRU” on page 116.

Symptom: Battery FRU is new, but will not hold a charge.1. Possible Cause: Battery charger board failure.


b. If this does not solve the problem, go to Possible Cause 2.

2. Possible Cause: Faulty battery harness.

a. Replace both power supplies using the instructions on “Replacing a FailedPower Supply” on page 122.

b. Allow the system to run for at least 24 hours in order to properly charge thebatteries. If this does not solve the problem, replace the battery harnessusing the instructions on “Replacing the Battery Harness” on page 125.

Symptom: Loss of battery backup during a power outage.1. Possible Cause: Battery failure or battery FRU is missing.


Symptom: No power to the controller module (all Power LEDsoff).1. Possible Cause: Power switches turned off.

a. Turn on both power switches on the controller module.


b. Turn on the main circuit breakers in the rackmount cabinet, if applicable.

2. Possible Cause: Power cords unplugged.

a. Check to make sure all power cords are plugged in securely.

3. Possible Cause: Rack power failure.

a. Go to the power MAP for the rack in Seascape Solution Rack, Installationand Service Guide, IBM 2101 Model 100, SY27-7606.

4. Possible Cause: Power supplies overheated or failed.

a. Wait 10 minutes. If the power supplies turn on automatically, use therecovery procedure on “Recovering from a Power Supply Shutdown” onpage 121. If not, go to step 4.b.

b. Go to “Replacing a Failed Power Supply” on page 122 and replace thepower supplies.

Symptom: One power supply LED (FRU) is on and the other isoff.1. Possible Cause: Power supply is turned off or unplugged.

a. Plug in the power cord and turn on the power switch. If the LED remains off,go to Possible Cause 2.




Symptom: Power Supply LED (front) is on.1. Possible Cause: Power supply is missing or not plugged in properly.

a. Insert and lock the power supply into place. If the fault LED is still on, go toPossible Cause 2.




Symptom: Power is on and working in the rackmount cabinet,but the controller module has no power.1. Possible Cause: Controller module is unplugged or turned off.

a. Plug in both power cords and turn on both power switches. If this does notresolve the problem, go to Possible Cause 2.


a. Check the power supply LED on the front cover. If it is on, go to the nextstep. If not, go to the next symptom.

b. Look at the LEDs on both power supply FRUs. If a Fault LED is on, replacethe failed power supply using the instructions on “Replacing a Failed PowerSupply” on page 122. If both are off, go to the next symptom.

Chapter 7. Reference 137

Symptom: The power supply FRUs LEDs are on, but all the otherFRU LEDs are off.1. Possible Cause: Defective DC power harness.

a. Replace the DC power harnesses using the instructions on “Replacing theDC Power Harnesses” on page 128. If this does not resolve the problem, goto Possible Cause 2.

2. Possible Cause: Defective power interface board.

a. Replace the power interface board using the instructions on “Replacing aController Module Chassis” on page 131.


Part 4. Drive Module Service Guide


Chapter 8. Getting Started with the Drive Module

This chapter contains introductory information about the Drive Module, with its partsand features.

What is the Drive Module?

The Drive Module (Figure 70) is a compact unit that provides high-capacity diskstorage for Small Computer System Interface (SCSI, pronounced “scuzzy”) busenvironments. It delivers fast, high-volume data management functions to single ordual host controllers by storing and retrieving data across multiple drives. Designedfor continuous and reliable service, the drive module’s redundant disk drives, powersupplies, and fans have Hot Swap capability for easy replacement without shuttingdown the system. All drive modules contain:

v Up to ten disk drives: 4.5 GB, 9 GB, or 18 GB

v Redundant power supplies

v Redundant fans

v Over-temperature indicator

v Easy-to-use controls and field replaceable units (FRUs, pronounced “frews”)

v SCSI interface

The drive module supports wide, ultra2-SCSI for both the host SCSI interface anddrive channels. The drive interface is single-ended (SE) and the host interface ismultimode low voltage differential/SE (LVD/SE). This host interface provides acommon link between an LVD host controller and SE SCSI drive modules.Designed for easy installation and integration into a wide range of systemenvironments, the drive module can support a variety of styles and configurations.

The remaining sections in this chapter describe these and other features.

Figure 70. Drive Module


Basic Components

This section provides a brief description and reference pages for the drive module’sprimary components.

Front View

There are two primary components on the front of the drive module (Figure 71):

v Front panel – a decorative panel that contains twenty light emitting diodes(LEDs), two per drive FRU. See “Front Panel” on page 143.

v Drive FRUs – ten portable containers for disk drives. See “Drive FRUs” onpage 144.

Back View

There are three primary components (Figure 72) on the back of the drive module:

v Fan FRUs – two portable containers for the cooling fans. See “Fan FRUs” onpage 151.

v Power Supply FRUs – two portable containers for the power supplies. See“Power Supply FRUs” on page 149.

v Interface FRUs – a portable container for an ESM board. See “EnvironmentalServices Monitor Board” on page 146.

Figure 71. Front Views of the Drive Module


About the Drives

There are three types of drives that may be used in a drive module:

v 16-bit, 4.5 GB SCSI disk drives

v 16-bit, 9 GB SCSI disk drives

v 16-bit, 18 GB SCSI disk drives

The rackmount drive module supports up to ten drive FRUs. The status lights for alldrive FRUs are located on the front panel.

Front Panel

The front panel (Figure 73) contains the Drive LEDs that indicate the drive’s status.

There are twenty LEDs on the drive modules’s front panel (Figure 73), two aboveeach drive slot:

v Active LEDs , green lights that glow intermittently during SCSI activity to andfrom the drive and blink to identify the drive after the host issues a ″DriveIdentify″ command.

v Power/Fault LEDs , dual-color LEDs that (a) glow green when there is power tothe drive, (b) glow amber when there is a drive failure.

Figure 72. Back View of the Drive Module

Chapter 8. Getting Started with the Drive Module 143

Drive FRUs

All disk drives are housed in portable drive FRUs (Figure 74). Each drive FRU plugsdirectly into one of ten drive slots on the front of the drive module and has amulti-function lever that serves as:

v A handle and lock for inserting and removing the drive

v An air vent for circulating air to the drives

Drive Numbering

Each disk drive has a unique drive channel number and drive SCSI ID number,based on the drive’s physical location (Figure 75). In a basic setup, there are twodrive channel numbers per drive module (channels 1 and 2), with five drive SCSI IDnumbers per drive channel (IDs 0–4). However, some installations with multipledrive modules require the drive modules to be configured with a single drivechannel. In these cases, all drives in the module will be logically connected on asingle SCSI bus and each will have a unique SCSI ID (IDs 0–4 and 8–0xC). Referto Figure 75 on page 145 for more detailed information.

The Drive FRUs plug into the drive slots and directly into the drive module’smid-plane, which automatically sets the drive channel and SCSI ID numbers. Drive

Figure 73. Drive LEDs

Figure 74. Drive FRU


modules use the Option switches to configure the modules in one of two ways: two5-drive buses, or one 10-drive bus. The SCSI ID numbers for the two 5-drive busesare 0–4 for each bus, and for the one 10-drive bus, the SCSI ID numbers are 0–4and 8–0xC. For information about setting ID switches, see Step 5 of “Installing theDrive Module” on page 49.

Drive Capacities

Table 31 lists the storage capacity for 4.5, 9 and 18 GB drives.

Table 31. Drive Capacities

Drive Formatted Capacity (Bytes) Sector Size (Bytes)

4.5 GB 4.56 x 10⁹ 512

9 GB 9.13 x 10⁹ 512

18 GB 18.35 x 10⁹ 512

For additional drive-related information, refer to the following sections:

Figure 75. Drive Channel and SCSI ID Numbering


v Replacing a failed drive or drive-related components, see “Maintaining theDrives” on page 160

v Drive SCSI ID designations, refer to “Drive Numbering” on page 144

v Troubleshooting SCSI interface problems, see “Hints for TroubleshootingInterface Problems” on page 169

About the SCSI Components

The drive module contains or uses several SCSI components. These componentsinclude the following hardware elements:

v One ESM board

v Interface cables (SCSI bus)

v One mid-plane

These components attach the drive module’s drive FRUs to the host controllers orother devices on the SCSI bus and provide a communication link for transferring I/Oto and from the drives. The remainder of this section describes the basic features ofthese SCSI components.

Environmental Services Monitor Board

Drive modules configured as disk storage units for connection to a host controllercontain drive FRUs and an Environmental Services Monitor (ESM) board. The ESMboard provides a SCSI interface to the drives and monitors the drive module’soverall status.

ESM FRU

The ESM board comes in a portable ESM FRU (Figure 76). The ESM FRU fits intothe slot on the back of the drive module and plugs directly into an internal interfaceboard called the mid-plane (refer to “Mid-Plane” on page 148). Two levers lock theFRU in place.

The ESM FRU has several connectors, switches, and LEDs (Figure 77), including:

Figure 76. ESM FRU


v SCSI connectors: two 68 pin VHDCI for SCSI bus cables

v Tray ID switch: a binary, rotary switch that sets the drive module’s tray ID number

v Option switches: five 2-position switches that enable or disable drive interfacefunctions on the ESM board (For a detailed description of these switches, seeTable 35 on page 191).

v Power LED : a green light that glows when there is power to the board

v Over Temp LED : an amber light that glows when the drive module is overheated

ESM Board Features: The ESM board performs two primary functions:

v Providing SCSI interface connections between the drives and the SCSI bus

v Supplying environmental status information to the host

To perform these functions, the board uses three types of chips:

v Interface chip

v SCSI Accessed Fault Tolerant Enclosure (SAF-TE, pronounced “safety”) chip

v Temperature monitor chip

The interface chip isolates the drive SCSI buses from the host and converts thesingle-ended drive bus to a multimode, low-voltage, differential/single-ended(LVD/SE) host bus. This interface includes two SCSI connectors and a Tray IDswitch that allows you to attach several hosts to one drive module.

There are two SAF-TE chips that provide the control logic needed to monitor andmanage the physical and internal environment characteristics of the drive module.These chips accept input from external sensors, and monitor both device status and“in-place” lines. In addition, they allow the host to control the visual indicators forthe drives.

Each SAF-TE chip monitors the following environmental conditions:

v Presence or absence of drive FRUs:

– With two five-drive buses, there is a SAF-TE chip for each bus

– With one ten-drive bus, both chips are on the same bus and monitor 5 driveseach

Figure 77. ESM Board Connectors, Switches, and LEDs


v Presence or absence of two power supply FRUs and two fan FRUs

v Fault lines for five drive FRUs, which includes blinking the LED to identify aspecific drive

v Operational status lines for the power supplies and fans

v Temperature levels

The temperature monitor chip continuously checks the temperature inside the drivemodule and activates an alarm signal when one of the following occurs:

v Internal temperature rises above 40 ° C (104° F). If this occurs, the temperaturemonitor sets the Enclosure Temperature Alert (ETA) bit to 1, which turns on theamber Fault LED on the ESM FRU.

v Internal temperature rises above 50 ° C (122° F). If this occurs, the temperaturemonitor reports a second sensor status to the host through the Vendor UniquePass-Thru (VUPT) byte, which also contains drive channel number, SCSI ID, andUPS status line assignments (see Table 32).

Table 32. VUPT Byte Assignments

Bit/Byte

7 6 5 4 3 2 1 0

0 UPS-inpl* Too_hot(>50°C)

Diffsense StateLVD = High SE= Low

Bus_ID Modid_3 Modid_2 Modid_1 Modid_0

For additional information topics relating to the ESM board, refer to:

v Replacing a failed ESM board, see “Replace a Failed ESM FRU” on page 170.

v Determining and changing drive IDs and other interface options, see “DriveNumbering” on page 144 and Step 5 of “Installing the Drive Module” on page 49.

v Troubleshooting SCSI interface problems, see “Hints for TroubleshootingInterface Problems” on page 169.

Mid-Plane

The mid-plane is the primary interconnect board inside the drive module (seeFigure 78). The mid-plane provides power and SCSI interface connections betweenthe drives, power supplies, fans, and ESM board. The mid-plane has fifteenconnectors:

v Ten front connectors for the drives

v Five back connectors for the ESM board, two power supplies, and two fans


Interface Cables

The drive module uses two SCSI bus cables. For more information on interfacecables, refer to the following:

v Troubleshooting the SCSI components and cables, refer to “Hints forTroubleshooting Interface Problems” on page 169.

v Technical information regarding interface cables and details about drive SCSI IDsand interface options during drive module installation, refer to “Chapter 14.Technical Reference” on page 191.

About the Power System

The drive module’s power system consists of two power cords and two powersupplies.

Power Supply FRUs

The power supplies provide power to the internal components by convertingincoming AC voltage to DC voltage. Both power supplies are removable powersupply FRUs that slide into either of the two slots on the back of the drive module.The power supplies are interchangeable (with reversible levers) and plug directlyinto the mid-plane inside the drive module (see “Mid-Plane” on page 148).

Each power supply FRU (Figure 79 on page 150) has a locking lever, plus one:

v Power connector, a socket for attaching the incoming AC power cord

v Power switch, that turns the power on and off

v Power LED , a green light that glows when the power switch is turned on

v Fault LED , an amber light that glows when one of the following occurs:

– Power is off with one power supply FRU; the second FRU is plugged in andturned on

Figure 78. Location of Mid-Plane


– After a power failure

– The power supply fails

Each power supply FRU uses one power cord. You can connect each cord to anindependent power source or connect both to a common power source. The powersupplies use active current sharing. This means that one power supply will maintainelectrical power to the drive module if the second power supply is turned off ormalfunctions. In addition, redundant power supplies support hot swapping, a featurethat allows you to replace a failed power supply while the system is powered-upand running.

For additional information on topics related to the power system, refer to:

v Turning the power on and off, see “Turn On the Power” on page 153 and “TurnOff the Power” on page 154.

v Recovering from a power failure, see “Restore Power After an Emergency” onpage 156 or “Recover from a Power Supply Shutdown” on page 180.

v Replacing a failed power supply, see “Replace a Failed Power Supply” onpage 183.

v Reviewing drive module power requirements, see the power requirements sectionon “Electrical” on page 39.

v Troubleshooting the power system, see the “Drive Module Troubleshooting Chart”on page 198.

Figure 79. Power Supply FRU


About the Cooling System

The drive module’s cooling system consists of two fan FRUs, each containing twofans.

Fan FRUs

The fan FRUs (Figure 80) circulate air inside the drive module by pulling air inthrough the vents on the front of the drive FRUs and pushing the exhaust out thevents in the back of each fan FRU. Each FRU is removable and has a latch andhandle, plus:

v Air vents , exhaust holes that allow air to exit the chassis through the fans

v Fault LED , an amber light that glows during a fan failure

The fan FRUs are interchangeable and slide into one of the two slots on the backof the drive module. They mount in opposite orientations and plug directly into themid-plane inside the drive module. Like power supplies, the fans are redundant andcan be hot swapped while the drive module is turned on and running, as long asthe exchange is completed within 15 minutes . If one fan FRU fails, the secondfan FRU continues to operate. For additional information on topics related to thecooling system, refer to:

v Replacing a failed fan, see “Replace a Failed Fan” on page 188

v Reviewing drive module environmental requirements, refer to “Heating and AirConditioning” on page 38

v Troubleshooting the cooling system, see “Drive Module Troubleshooting Chart” onpage 198

Moving The Drives

If a drive drawer is being moved to another subsystem, you must remove theconfiguration information written on the drives to avoid problems. Make sure that allthe drives in the drawer being used are ″unassigned″ or ″non-existent″ (not part ofany drive groups or LUNs) before moving. Have the customer use the storagemanagement software to remove the drives in the drawer being moved from the

Figure 80. Fan FRU


existing configuration. If the host connection is not available or alreadydisconnected, you can use DOS RAID Manager (DRM) to perform these operations.

Important: If the ″Reset Configuration″ option is used to delete the configurationinformation on the drives, be aware that this function results in thecreation of a default LUN 0. You must delete this LUN after the resetconfiguration function completes.


Chapter 9. Operating the Drive Module

This chapter describes the user controls and provides basic operating instructions.

Basic Operation

The drive module has several features that enable you to operate and service thehardware. These include:

v LEDs , green or amber lights that glow or blink to indicate either a normaloperating status or a hardware error

v Switches , controls that turn the power off and on, and select interface options forthe drive module

v Connectors , sockets for attaching interface and power cables to the drivemodule

v Handles and levers , that allow you to remove and install individual FRUs moreeasily

This section explains how to use these controls to turn the drive module on and offunder normal and emergency circumstances.

Controls on the Front

The primary user controls on the front of the drive module are the LEDs and thedrive FRU levers. For detailed descriptions of these parts, refer to the followingsections:

v “Front Panel” on page 143

v “Drive FRUs” on page 144

Controls on the Back

There are five FRUs accessible from the back of the drive module. All thesecomponents contain several user controls. For detailed descriptions of these parts,refer to the following sections:

v “Environmental Services Monitor Board” on page 146

v “Power Supply FRUs” on page 149

v “Fan FRUs” on page 151

Turn On the PowerNotes:

1. If you are turning on the drive module after an emergency shutdown or poweroutage, use the procedure in “Restore Power After an Emergency” on page 156.

2. Controllers in a Fibre Channel Storage Server will not acknowledge anyattached drives that are powered-up after the controller module. Therefore, youmust turn on the drive modules before controller modules .

3. During the power-up process, the drive module LEDs may turn on and offintermittently. When power-up is complete, the green LEDs should be on andthe amber LEDs should be off.


Instructions

Use this procedure to turn on the drive module’s power.

1. When are you turning on the drive module?

v After a normal shutdown: Read the notes on page on page 153, then go toStep 2 below.

v At initial start-up. Read the notes on page on page 153, then verify thefollowing. When you are finished, go to Step 3 below.

– All cables and FRUs and are plugged securely into the drive module.

– The interface switches are set correctly (host SCSI ID, Option, etc.).

– The hosts, controller modules, and other devices are ready for power-up.

2. Turn on power (Figure 81).

Turn on both power switches on the back of the drive module. You must turn onboth switches to take advantage of the redundant power supplies. Go to Step 4.

3. Turn on power (Figure 81).

Subsystem components must be powered up in the correct sequence to ensureproper operation. Power up the components in the following order:

a. rack

b. hub (if applicable)

c. drive modules

d. controller module

e. host (wait until all the drives have spun up to speed)

Based on this power-up sequence, turn on the power to each device, includingapplicable circuit breakers in the rackmount cabinet. When it is time, turn onboth power switches on the back of the drive module, followed by the controllermodules. Go to Step 4.

4. Go to “Check the Overall Hardware Status” on page 156.

Turn Off the Power

Note: Except in an emergency, never turn off the power if any Fault LEDs arelit on the drive module, especially on the drive FRUs. Always use the

Figure 81. Power Cords and Switches


proper troubleshooting or servicing procedure to correct a fault before turningoff the power. This will ensure that the drive module will power up correctlylater. For guidance, refer to “Drive Module Troubleshooting Chart” onpage 198.

The drive module is designed to run continuously, 24 hours a day. Once you turn onthe drive module, it should remain on. The only time you should turn off the poweris when:

v Support personnel or instructions in a procedure tell you to turn off the power

v A power outage or emergency situation occurs (see “Perform an EmergencyShutdown”)

Instructions

Use this procedure to turn off the drive module’s power.

1. Do the following:

v Stop all I/O activity to the drive module and attached controllermodules . If applicable, logically disconnect the drive module from the host.Make sure that all the drive Active LEDs on the front panel and Fast WriteCache LEDs on applicable controller modules are off (not blinking).

v Make sure that all the drive module amber Fault LEDs are off. If a FaultLED is on, correct the problem before turning off the power (see “DriveModule Troubleshooting Chart” on page 198).

2. Turn off the power (Figure 81 on page 154).

Turn off both power switches on the back of the drive module. Wait at least tenseconds before you turn on the power again.

Perform an Emergency Shutdown

Attention: Emergency situations might include: fire, flood, extreme weatherconditions, or other hazardous circumstances. If a power outage or emergencysituation occurs, you should turn off the power switches on all computingequipment.

This will help safeguard your equipment from potential damage due to electricalsurges when power is restored. If the drive module loses power unexpectedly, itmay be due to a hardware failure in the power system or mid-plane (see “DriveModule Troubleshooting Chart” on page 198).

Instructions

Use this procedure to shutdown the drive module during an emergency.

1. Turn off all power switches and unplug the power cords (Figure 81 onpage 154).

If you have time, stop all activity to the drive module and check the LEDs (frontand back). Make note of any fault LEDs that are on so you can correct theproblem when you turn on the power again.

Turn off both power switches and unplug the power cords from the back of thedrive module. If applicable, turn off the main circuit breakers in the rackmountcabinet.

2. Go to “Restore Power After an Emergency” on page 156.

Chapter 9. Operating the Drive Module 155

Restore Power After an Emergency

Note: Controllers in a Fibre Channel RAID Storage Server will not acknowledgeany attached drives that are powered up after the controller module.Therefore, you must turn on the drive modules before the controllermodules.

Instructions

Use this procedure to restart the drive module after a power failure or emergencyshut down. The following instructions assume that you turned off the powerswitches on the drive module during an emergency situation or after a poweroutage occurred.

1. After the emergency situation is over or power is restored to the building, checkthe drive module for damage.

DO NOT continue with this procedure if you find any evidence of fire, water, orstructural damage. Depending on the current service agreements, you may ormay not need to send the unit back to the factory for repair/replacement. Callthe factory (or appropriate service organization) for assistance. If there is novisible damage, go to Step 2.

2. Plug in the power cords and turn on the power switches (Figure 81 onpage 154).

After you have checked for damage, plug in the drive module’s power cords.Turn on both power switches. During the power-up process, the drive moduleLEDs may turn on and off intermittently. When power-up is complete, the greenLEDs should be on and the amber LEDs should be off.

3. Check the LEDs on the front and back of the drive module.

Check all of the LEDs on the front panel and on all of the FRUs on the back ofthe drive module. The green LEDs should be glowing and the amber LEDsshould be off. If one or more Fault LEDs turn on, go to “Drive ModuleTroubleshooting Chart” on page 198 for instructions.

Checking the Drive Module

This section tells you how to check the status of the drive module LEDs.

Status LEDs

The drive module’s LEDs indicate the status of both the drive module and theindividual components within the drive module. The green LEDs indicate a normaloperating status; the amber LEDs indicate a hardware fault. It is important that youcheck all the LEDs on the front and back of the drive module when you turn on thepower. Besides checking for faults, you can use LEDs on the front panel todetermine if the drives are responding to I/O transmissions from the host.

Check the Overall Hardware Status

Instructions

Use this procedure to check the operating status of the drive module and itscomponents.

1. Check the LEDs on the front panel (Figure 82 on page 157).


Under normal conditions, all Power/Fault LEDs above the drives will be glowinggreen (read the following NOTE). If any Power/Fault LEDs turn amber, go to“Replace a Failed Drive” on page 160.

Note:

v If there is I/O activity to the drive module, the green Active LEDs willbe blinking above one or more drives.

v If you just turned on the power, the drive module’s green and amberLEDs may turn on and off intermittently as the drives spin-up. Waituntil the drive module has finished powering up before you beginchecking for faults.

2. Check the LEDs on the back (Figure 83 on page 158).

Under normal operating conditions, the green LEDs on all the FRUs are on andthe amber LEDs are off. If one or more amber Fault LEDs are on, refer to the“Drive Module Troubleshooting Chart” on page 198.

Table 33. Drive LEDs on Front Panel

LED LED Color Normal Operation ProblemIndicator

Service Page:

Drive FRU LEDs

Active Green Flashes when busy Never flashes “Maintaining the Drives” onpage 160, “Maintaining the SCSIComponents” on page 168

Power/Fault

Green On Off “Drive Module TroubleshootingChart” on page 198

Amber Off Steady glow “Maintaining the Drives” onpage 160

Figure 82. Drive LEDs on the Front Panel

Chapter 9. Operating the Drive Module 157

Table 34. LEDs on Drive Module with ESM Board

LED LED Color Normal Operation Problem Indicator Service Page #

Fan FRU LEDs

Fault Amber Off On “Maintaining theCooling Fans” onpage 187

Power Supply FRU LEDs

Power Green On Off “Turn On the Power”on page 153,“Maintaining thePower System” onpage 180

Fault Amber Off On “Maintaining thePower System” onpage 180

ESM FRU LEDs

Over Temp Amber Off On “Drive ModuleTroubleshootingChart” on page 198

Power Green On Off “Drive ModuleTroubleshootingChart” on page 198

TERM Power Green On Off “Drive ModuleTroubleshootingChart” on page 198

Bus Activity Green Flashes when busy Never flashes “Drive ModuleTroubleshootingChart” on page 198

Bus Mode (LVD/SE) Green On for LVD connectionOff for SE connection

Off for LVD connectionOn for SE connection

“Drive ModuleTroubleshootingChart” on page 198

Figure 83. LEDs on Drive Module with ESM Board


Chapter 10. Servicing the Drives

This chapter contains maintenance and repair procedures for the Drive Moduledrive FRUs.

Disk Drive Overview

The drive module supports up to ten drive FRUs. For detailed information about thedrive FRUs, refer to “Drive FRUs” on page 144.

General Notes

Here is a list of things to consider when servicing the disk drives:

v Use ESD protection — When handling drives, use appropriate protection(grounding strap, etc.) against electrostatic discharge (ESD).

v Use the correct type of drives — There are three types of drives that may beused in the drive module

– 16-bit, 4.5 GB SCSI disk drives

– 16-bit, 9 GB SCSI disk drives

– 16-bit, 18 GB SCSI disk drives

Check the applicable hardware and software documentation provided with yoursystem for restrictions regarding disk drive configurations. Logical Units (LUNs)will also be limited by the smallest size drive.

v Keep the drive away from magnets or magnetic fields — Magnetic fields willpermanently destroy all data on a drive and may cause irreparable damage tothe drive’s circuitry.

v Protect the drive and its connectors from sudden impacts, jolts, or shocks— Dropping or bumping the FRU can damage the disk drive. Avoid all contactwith the connectors or pins on the rear of the drive FRU. These connectors areeasily damaged.

v Install drives in one complete motion — When installing a drive FRU, makesure that you insert it all the way into the slot and lock the handle in place.Partial insertion of a drive may cause the host controller to mark other drives onthe same bus as failed.

v Remove drive FRUs only when necessary — Do not remove a drive FRUunless:

– the drive has failed and its Power/Fault LED is glowing amber

– it has a failed status in the host software

– you fail the drive manually, or

– you shut down the drive module before moving it to another location, or whileperforming a procedure in this book.

Note: In some cases where I/O has not been performed to a defective drive,diagnostics may report the drive problem, but the drive may not have afailed status in the host software and the Power/Fault LED may not beglowing amber. In these cases, you will have to manually fail the drivefrom the host before replacing it.


Attention: Never remove a drive FRU while its green Active LED is blinking.Doing so can cause data loss and may cause the host controller to mark thedrive as “failed.” If you remove an active drive accidentally, wait at least 10seconds before you reinstall the FRU.

v Remove the correct drive — Make sure that you remove the correct drive. Ifyou inadvertently remove the wrong drive, wait at least 10 seconds and replacethe drive.

Note: Failure to replace drive FRUs in their correct slot could result inreduced performance.

v Replace drives in the correct slots — If you remove drive FRUs for anyreason, you should replace each drive FRU in its original location beforerestarting the drive module. This means you must put each drive into the sameslot from which you removed it, based on its SCSI ID and channel number (see“Drive Numbering” on page 144). This precaution does not apply when you areremoving blank drive FRUs.

Drive Failure Notes

Here are things to consider when replacing a failed drive.

v Remove the failed drive ONLY — Never remove a drive FRU unless it:

– has failed and the Power/Fault LED is glowing amber, or

– has a failed status in the host software.

Make sure that you remove the failed drive, not a good drive. If you inadvertentlyremove the wrong drive, wait 10 seconds and replace the drive FRU.

v Wait at least ten seconds before installing a new drive — Once you remove afailed drive, wait a minimum of ten seconds before you install the new drive.

Maintaining the Drives

Drive problems include any malfunctions that delay, interrupt, or prevent successfulI/O activity between the hosts and the disk drives in the drive module. This includestransmission problems between the host adapters or host controllers, the drivemodule drives, and the ESM board. For the purposes of this discussion, the drivemodule’s drive-related components include:

v Disk drive FRUs

v ESM board FRU

The ESM FRU and all the drive FRUs have ″hot swap″ capability. This sectionexplains how to replace a failed drive. For other information about disk FRUs or theESM FRU, refer to the following:

v To learn about the drive FRUs, go to “About the Drives” on page 143.

v To replace a failed ESM board, refer to “Replace a Failed ESM FRU” onpage 170.

Replace a Failed Drive

Problem Indicators

There may be a drive problem when one or more of the following occur above adrive FRU:


v Front panel Power/Fault LED turns amber

v Front panel Power/Fault LED is off

v Front panel green Active LED turns off and remains off, even during I/Ooperations to that drive

Note: During a drive failure:

v If a single drive fails in a RAID 0 logical unit, you may lose all data in thatdrive group.

v If more than one drive fails at the same time in a RAID 1, 3, or 5 logicalunit, you may lose all the data in that drive group.

Tools/Equipment

Replacement drive FRU, grounding strap (or other antistatic protection device).

Instructions

Use this procedure to replace a failed drive FRU in the drive module.

1. If applicable, open the front panel (or door) on the cabinet to gain access tothe drive module.

2. Check the drive LEDs on the front panel (Figure 84 on page 162).

Choose one that best describes the LED status for the drive FRU:

a. Green Active LED is blinking and Power/Fault LED is glowing green.The drive is operating correctly. No action is required.

b. Both LEDs are off, but LEDs above other drives in this drawer are on.The drive may not be plugged in properly or the drive has failed. Verify thatthe drive is inserted all the way into the slot and the handle is locked inplace. If the drive is properly inserted, the go to Step 3 and begin replacingthe failed drive.

c. All LEDs are off above all drives in the drawer. There may be a problemwith the power system. Check for Fault LEDs on the back of the drivemodule, then go to “Drive Module Troubleshooting Chart” on page 198 forinstructions on correcting the problem.

d. Power/Fault LED is glowing amber. Go to Step 3 and begin replacing thefailed drive.

e. The Power/Fault LED is glowing green, but the host indicates a drivefailure. If the host has not performed any data I/O to the failed drive, thenit may not have failed the drive yet, but diagnostics or some other hostprocess may have detected that the drive is not functioning properly (forexample, running diagnostics after installing the subsystem). Go to Step 3and begin replacing the drive indicated by the host.

Chapter 10. Servicing the Drives 161

3. Read the technical information about drive failures.

Read “General Notes” on page 159 about handling drives and “Drive FailureNotes” on page 160. In addition, read the pertinent information in the FibreChannel Storage Manager software documentation regarding drive failures andrecovery procedures. Attention: Electrostatic discharge can damage sensitivecomponents. Use a grounding wrist strap or other antistatic precautions beforeremoving or handling the drive FRUs.

4. Put on a grounding strap.

5. Unpack the new drive.

Unpack the replacement drive FRU and set it on a dry, level surface near thedrive module and away from magnetic fields. Save the packing material in caseyou need to return the drive to the factory or local supplier.

6. Read the documentation shipped with the drive.

Find and read the documentation shipped with the new drive. Read all theprecautionary notes, kit instructions, and other information. Kit instructions oftencontain the most current information regarding the drives and their installation,plus upgrade or servicing procedures.

Note: Do not remove a drive FRU unless its Power/Fault LED is glowingamber or you have manually failed it through the host RAIDmanagement software. If you must manually fail the drive, follow theinstructions in the Fibre Channel Storage Manager User’s Guide for youroperating system:

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host, thenrefer to the section ″Manual Recovery/Drives″ in the ″Recovery″ chapterof the Fibre Channel Storage Manager and StorWatch Fibre ChannelRAID Specialist, User’s Guide, SC26-7285.

v If the subsystem is attached to an AIX host, then refer to the section″Failing a Drive″ in the ″Configuring the 2102 Fibre Channel RAID StorageServer″ chapter of the Fibre Channel Storage Manager, Installation andUser’s Guide for the AIX Operating System, SC26-7290.

7. Remove failed drive FRU (Figure 85 on page 163).

Remove only the failed drive.

8. Install the new drive (Figure 85 on page 163).

Make sure that at least ten seconds have passed since you removed the faileddrive. After ten seconds, install the new drive FRU.

Figure 84. Drive FRU and Front Panel LEDs


9. Check the LEDs above the new drive (Figure 84 on page 162).

After you insert the drive, both LEDs may turn on intermittently as the drivespins-up. Wait for the drive to complete the spin-up process, then choose one ofthe following that best describes the behavior of the drive LEDs:

a. Active LED is blinking and Power/Fault LED is glowing green. Yoursystem is reconstructing the drive automatically (See Note below).Depending on the size of the drive and amount of data to be restored,reconstruction could take several minutes. Wait for the system to completethe reconstruction process. The Active LED will stop blinking and thePower/Fault LED will be glowing green. Go to Step 11 on page 164.

b. Active LED is off (never blinked) and Power/Fault LED is glowing green.Your system is not reconstructing the drive automatically. Go to Step 12 onpage 164.

c. Active LED is off and Power/Fault LED is glowing amber . Wait twominutes to give the system ample time to spin-up and, if applicable,reconstruct the drive (See Note below). If the Power/Fault LED continues toglow amber, remove the new drive FRU, wait at least ten seconds , andre-install it. If the Power/Fault LED turns green and the Active LED startsblinking, go to Step 9.a (above). If the Power/Fault LED turns green, but theActive LED does not start blinking, go to Step 12 on page 164. If thePower/Fault LED remains amber, go to Step 10.

Note: Depending on the configuration of the drive module and the parameters setin the host RAID management software, the drive may begin reconstructingautomatically as soon as you install it in the drive slot. During this process,the drive’s Power/Fault LED might turn amber and stay on for a few minutes,then turn green when the Active LED begins blinking. A blinking Active LEDindicates that the data reconstruction is in progress. When the Active LEDstops blinking, the reconstruction is complete and you can resume thisprocedure at Step 11 on page 164. If this does not occur, go to Step 12 onpage 164.

10. Determine if the new drive is defective.

If you re-installed the drive and the Power/Fault LED is still glowing amber, itmeans

Figure 85. Removing/Installing Drive FRUs


v the operating system or host RAID management software has notacknowledged the new drive, or

v the new drive is defective

Do the following:

a. If the subsystem is attached to a Windows NT, SUN, or HP-UX host, thenuse the Recovery application of the Fibre Channel Storage manager hostsoftware to check the drive’s status and to perform the appropriaterestoration tasks required by the system.

If the subsystem is attached to an AIX host, then run the diagnostics to tryto isolate and correct the problem. If the problem is corrected, go to Step13.

If not, go on to Step 10.b.

b. The new drive FRU has failed. Replace this drive with another drive FRU.If replacing the drive does not solve the problem, go to “Identify OtherDrive-Related Problems”.

11. Your system reconstructed the drive automatically.

Once the data reconstruction is complete (the Active LED stops blinking andthe Power/Fault LED glows green), use the Fibre Channel Storage Managerhost software or RAID Manager for DOS to check the drive module’s status(see “Checking Array Status” on page 226). If the drive and drive module havea normal status, go to Step 13. If the software displays an error status, followthe recovery procedure that is given.

12. Your system did not reconstruct the drive automatically.

v If the subsystem is attached to an AIX host, then refer to the procedures forreplacing drives and restoring and recovering logical units in Fibre ChannelStorage Manager, Installation and User’s Guide for the AIX OperatingSystem, SC26-7290.

v If the subsystem is attached to a Windows NT, SUN, or HP-UX host, thencontinue on with this procedure.

What type of logical units did the failed drive (the one you just replaced)contain?

v RAID level 1, 3, or 5 LUNS. Use the Recovery Application of the FibreChannel Storage Manager host software to reconstruct the data on the newdrive manually. Once the reconstruction process is complete, check theoverall status of the drive module. If the drive and drive module have anormal status, go to Step 13. If the software displays an error status, usethe Recovery Application and follow the recovery procedure that is given.

v RAID level 0 LUNS. If the logical units on the replaced drive were RAIDlevel 0 units, you must reformat the LUN. Use the Recovery Application andfollow the recovery procedure that is given.

13. Return to normal operation.

Close the panels (or doors) on the cabinet, if applicable.

Identify Other Drive-Related Problems

Problem Indicators

There may be a drive-related problem with the ESM board or mid-plane when oneor more of the following occur:


v All or some Active LEDs remain off on drives connected to the same SCSI bus,or during either I/O operations or “drive identify” commands from the host

v All drive FRU Power/Fault LEDs are glowing green, yet the operating system orhost software indicates an I/O error or drive fault

v Host is unable to access the drives on one or more SCSI buses

Instructions

Use this procedure to diagnose drive-related problems in the drive module. Thisprocedure assumes that:

v You have attempted to access the drive module drives from the host controllerswithout success,

v You have checked all SCSI cables for defects and loose connections,

v You replaced a failed drive using the procedure in “Replace a Failed Drive” onpage 160 and it did not solve the problem, or

v The operating system or host software issued a drive error, yet all thePower/Fault LEDs for the drives remain green (instead of turning amber).

1. Check for faults.

If applicable, open the panels (or doors) on the front and back of the cabinet togain access to the drive module. Check the drive LEDs and choose one of thefollowing:

v Power/Fault LED is amber (steady glow) . Go to “Replace a Failed Drive”on page 160.

v Power/Fault LED is green (steady glow), active LED is not blinkingduring I/O operations . Go to Step 2.

v All drive FRU LEDs are off . Go to Step 3 on page 166.

2. Check the drive module components.

The drive Active LEDs are not blinking during I/O operations to the drives, yetall the drive module’s amber Fault LEDs are off. This may indicate a failure ofthe ESM board, the mid-plane, or other SCSI component on the bus. Do thefollowing:

a. Read “Hints for Troubleshooting Interface Problems” on page 169.

b. Try to access the drives from the host by sending test data or “identify drive”commands from the Fibre Channel Storage Manager host software toindividual drives or all drives on each SCSI bus (see the entry for ″IdentifySubsystem Components″ in the 2102 Fibre Channel RAID Storage ServerStart Table D, in “Chapter 1. Maintenance Starting Points” on page 3). Then,choose one of the following:

v The appropriate drive or drives responded, yet the Active LEDsremained off. This probably means that the drive Active LEDs haveburned out. The only way to correct this problem is to replace the drivemodule’s mid-plane, a major repair operation (see “Replace a FailedMidPlane” on page 173).

v The drive or drives did not respond. Go to Step 2.c.

c. Make sure that the SCSI cables are connected securely to the drive module,that the drive module is logically connected to the host controllers, and thatthe hosts are transmitting to other devices on the SCSI bus without error. Ifeverything seems okay and the drives are not responding, go to Step 2.d onpage 166.


d. Use the Fibre Channel Storage Manager host software, to check the statusof all drives. Then, choose one of the following:

v A drive fault status appeared. This probably means that there is a drivefailure, but the amber light in the Power/Fault LED burned out. See“Replace a Failed Drive” on page 160.

v A host controller fault status appeared. This probably means that thereis a host controller failure, but the amber Fault LED on the host controllerFRU is burned out. Go to “Replacing a Failed Controller” on page 93.

v No drive fault indicated (host software may or may not show otherproblems). There may be a hardware malfunction with the host controller,ESM board, or mid-plane. Replace the host controller FRU (see“Replacing a Failed Controller” on page 93) or the ESM board (see“Replace a Failed ESM FRU” on page 170) first.

Note: The only way to correct a burned out drive LED is to replace thedrive module’s mid-plane, which is a major repair operation thatrequires the drive module being shut down (all I/O stopped).

3. Check the drive module for other faults.

Look at the LEDs on the back of the drive module and choose one:

v All drive module green and amber LEDs are off . Go to Step 4.

v One or more amber LEDs are glowing on the back of the drive module.Go to “Drive Module Troubleshooting Chart” on page 198.

v All green LEDs are on and the amber LEDs are off (on the back of thedrive module). There may be a hardware malfunction with the ESM board ormid-plane. Replace the ESM board (see “Replace a Failed ESM FRU” onpage 170) first.

4. Check the AC power source.

All drive module LEDs are off. This may indicate a power problem. Check thefollowing:

v Make sure that both of the drive module’s power cables are undamaged andplugged in, and both power switches are turned on.

v If applicable, check other devices in the cabinet and the UPS to make surethey have power and that the main circuits are turned on.

v Check the rack power. See the power MAP for the rack in the SeascapeSolution Rack, Installation and Service Guide, IBM 2101 Model 100,SY27-7606.

v Check the building’s main circuit breaker and outlet to verify that there ispower to the drive module.

v Replace both power supply FRUs (see “Replace a Failed Power Supply” onpage 183). If this does not solve the problem, the mid-plane may have failed.


Chapter 11. Servicing the SCSI Components

This chapter contains servicing procedures for the SCSI cables, ESM board, andmid-plane.

SCSI Component Overview

The Drive Module supports the ESM (environmental service monitor) interfaceboard.

For detailed information on the ESM FRU, refer to “Environmental Services MonitorBoard” on page 146.

Servicing SCSI Components

ESM FRU Servicing Notes

Before replacing a failed ESM FRU, be aware of the following:

v Use proper equipment and precautions against electrostatic discharge before youremove and handle the ESM FRU.

v Always stop all I/O activity to the drive module and turn off the power before youreplace the ESM FRU. See “Stopping I/O to the Drives” on page 168.

v Make sure that the new ESM FRU has the same Option and Tray ID switchsettings as the failed board you are replacing.

Attention: Failure to set the IDs properly could result in data loss on one or alldrive modules.

Mid-Plane Servicing Notes

Before you replace a failed mid-plane, you should be aware of the following:

v Use proper equipment and precautions against electrostatic discharge before youremove and handle the mid-plane or any other components in the drive module.

v Always stop all I/O activity to the drive module’s drives before you shut down thedrive module. See “Stopping I/O to the Drives” on page 168.

SCSI Cable Servicing Notes

Before you replace a SCSI cable, you should be aware of the following:

v Use proper equipment and precautions against electrostatic discharge before youremove and handle the SCSI cable or any other components in the drive module.

v You must stop all I/O activity to the drives connected to the SCSI cable beingreplaced if the drives connected to the SCSI cable:

– are part of a RAID 0 LUN

– include both drives in a mirrored pair of a RAID 1 LUN

– include 2 or more drives in a RAID 3 or RAID 5 LUN

If you are unsure of the LUN configuration, then you should stop I/O to theaffected drives to be safe. See “Stopping I/O to the Drives” on page 168.

v The drives connected to a specific SCSI cable will all have the same SCSIchannel ID. The SCSI channel ID will correspond to the SCSI connector that the


cable is connected to on the back of the controller module. A single SCSIchannel is connected to either 5 or 10 drive slots, depending on the setting of theBridge Disable option switch on the back of the drive module. Refer to “DriveNumbering” on page 144 and “LVD-SCSI Drive Cable Routing Examples” onpage 59 for more information and examples.

Stopping I/O to the Drives

In order to stop I/O to a specific set of drives, you must have the customer stop allapplications from all hosts that attempt to access the LUNs contained on theaffected drives. On an HP-UX, SUN or AIX host system, you should ensure that thecustomer has stopped using all file systems and logical volumes on the LUNscontained on the affected drives. You can use the Fibre Channel Storage Managersoftware for your operating system to determine the drives that make up each LUN.

As an added precaution on HP-UX, SUN and AIX host systems, you can unmountthe file systems and vary off volume groups on the LUNs containing the affecteddrives to ensure that there is no I/O to the drives.

Wait at least 1 minute after stopping I/O to ensure that data cached in the controllerhas been offloaded to the array. Once the I/O has been halted to a set of drives,the drive activity lights above each of the affected drives will remain off.

Maintaining the SCSI Components

SCSI component problems include any malfunctions that delay, interrupt, or preventsuccessful I/O activity between the hosts and other SCSI devices on the bus. Thisincludes transmissions between the drive module’s ESM board and the drive FRUsinside the cabinet. For the purposes of this discussion, the drive module’scommunication system includes the following elements:

v SCSI bus cables

v ESM board

v Midplane assembly

Types of Interface Problems

Interface problems on any computer system can be divided roughly into two maincategories: software-related problems and hardware-related problems.

Software-related problems that hamper communications typically involve one ormore of the following elements:

v Host operating system software error

v Disk array or other application error

v Incorrect configuration settings

Hardware-related problems that might disrupt communications include the followingelements:

v Loose, disconnected, damaged SCSI cables or connectors

v Improper interface switch settings

v Failed ESM board

v Drive failure or other device failure on the SCSI bus

v Failed mid-plane inside the drive module


v Failed host adapter board

Hints for Troubleshooting Interface Problems

The first step in correcting a communication problem is to determine the source ofthe problem. This means you need to decide if there is a problem with the hardware(physical equipment) or with the software (operating system or disk arrayapplication). The easiest way to do this is to try the following:

v If the problem occurred during or immediately after a software activity, try to undowhatever the software did, then step through each software function (in smallerincrements) until the problem occurs again. This will help you identify the functionthat is working incorrectly.

v If the problem occurred without an apparent software-related activity, check theoperating system and host software for error messages and associatedprocedures. This may help you determine if it is a software or hardware problem.

v Check the drive module for faults (see “Check the Overall Hardware Status” onpage 156). If any amber LEDs are on, go to the “Drive Module TroubleshootingChart” on page 198 for instructions.

Note: Verify that the Tray ID and Bridge Disable option bit are both set correctly onthe back of the ESM module. See Step 5 of “Installing the Drive Module” onpage 49 for more information.

v Check all the interface cables, particularly the SCSI cables, to make sure thatthey are securely connected and undamaged.

v If you were sent here from “AIX Error Codes (SRNs)” on page 15, then return tothe entry that sent you here. Otherwise, continue below.

Interface problems that may be harder to detect include: SCSI cables,malfunctioning ESM board, or mid-plane. If you have checked all the componentslisted above and cannot identify the problem, try the following:

v Replace the appropriate SCSI interface cables following the procedure in“Replace a SCSI Interface Cable”.

v Replace the ESM FRU following the procedures in “Replace a Failed ESM FRU”on page 170.

v Replace the mid-plane following the procedures in “Replace a Failed MidPlane”on page 173.

The following sections explain how to replace SCSI cables, an ESM FRU or amid-plane in the drive module. For additional information relating to SCSIcomponents and interfaces, refer to the following:

v To learn about the interface cables, go to “Interface Cables” on page 149.

v To learn about the ESM FRU, go to “Environmental Services Monitor Board” onpage 146.

v To learn about the mid-plane, go to “Mid-Plane” on page 148.

Replace a SCSI Interface Cable

There may be indication of a problem with the SCSI Interface cable if one or moreof the following occur:

Chapter 11. Servicing the SCSI Components 169

v Intermittent or no I/O activity is reaching the drives connected on this SCSIchannel

v Software reports I/O related errors

Tools and Equipment

The replacement SCSI cable, grounding strap (or other antistatic protection device),small flathead screwdriver, labels for cables (optional).

Instructions

Use the following procedure to replace a SCSI cable:

1. Read “SCSI Cable Servicing Notes” on page 167.

2. If applicable, remove the panels (or open the doors) on the back of the cabinetto gain access to the SCSI cables.

3. If necessary, stop all I/O activity to the drives on the affected drive channel (See“SCSI Cable Servicing Notes” on page 167).

4. Using a grounding strap, disconnect the SCSI cable from both the drive moduleand the controller module. Attention: If you are replacing more than one SCSIcable, then you should remove and replace a single cable before continuing onto the next. Improper cable connections could result in data loss.

5. Unpack and install the new SCSI cable. Make sure the cable is plugged insecurely in the same location as the original cable.

6. If applicable, replace the panels (or close the doors) on the back of the cabinet.


Use the Fibre Channel Storage Manger host software to verify the drive status andrestart I/O if necessary.

Replace a Failed ESM FRU

Problem Indicators

There may be a problem with the ESM FRU if one or more of the following occur:

v Amber LED is lit on ESM FRU when there is no over-temperature condition

v Intermittent or no I/O activity is reaching the drive module drives


Tools/Equipment

The replacement ESM FRU, grounding strap (or other antistatic protection device),and labels for cables (optional).

Instructions

Use this procedure to replace a failed ESM FRU.

1. Read “ESM FRU Servicing Notes” on page 167.

2. If applicable, remove the panels (or open the doors) on the front and back ofthe cabinet to gain access to the drive module.

3. Check the LEDs on the drive module and answer the following questions:

Is the amber LED lit on the ESM FRU?

v Yes. The drive module is overheated. Go to Step 5 on page 171.


v No. The operating temperature is normal. Answer the next question.

Are other amber LEDs lit on the drive module?

v Yes. Go to the appropriate procedure to replace the failed hardwarecomponent. Refer to “Drive Module Troubleshooting Chart” on page 198 forguidance.

v No. Go to Step 4.

4. Answer the following questions.

Has the operating system or Storage Manager software issued an errorrelating to the ESM board or I/O transmission to the disk array?

v Yes. Go to Step 6.

v No. Answer the next question.

Can you perform I/O operations to the drives successfully?

v Yes. Return to normal operation.

v No. Read “Hints for Troubleshooting Interface Problems” on page 169 andtry to determine the source of the interface problem. If you still cannotdetermine the source of the problem, go to Step 6 and replace the ESMFRU.

5. Check the fans and ventilation in the cabinet.

Check the LEDs on both fan FRUs. If one or both amber LEDs are lit on thefan FRUs, go to “Replace a Failed Fan” on page 188 to replace the failed fanFRU. If the amber LEDs are off, then check the ambient temperature insidethe cabinet to make sure it is within the required operating range (5° C to 40°C [41°F to 104°F]). If it is too hot, shut down the drive module and takenecessary steps to cool the environment. If the fans are working and thetemperature is within the normal operating range, go to Step 6.

6. Shut down the drive module (Figure 87 on page 172).

If applicable, stop all I/O activity to the drive module and logically disconnectthe drives from the host. Turn off both power switches and unplug both powercords from the back of the drive module. All LEDs should be off.

7. Disconnect the interface cables (Figure 87 on page 172).

Figure 86. Amber Fault LEDs (Rackmount)


You should label each SCSI cable with the appropriate bus number.Attention: You must reconnect the SCSI cables exactly as they wereconnected before you serviced the ESM FRU. Improper cable connectionscould result in data loss.

Electrostatic discharge can damage sensitive components. Use a groundingwrist strap or other antistatic precautions before removing or handling the ESMFRU or other drive module components.

8. Use a grounding strap and remove the ESM FRU (Figure 88 on page 173).

9. Prepare the new ESM FRU (Figure 88 on page 173).

Unpack the new ESM FRU and set its Option and Tray ID switches exactly asthey are set on the failed ESM FRU. Attention: Failure to set the BridgeDisable option switch correctly could result in data loss. You must set Optionswitches #1 and #2 on the new ESM FRU EXACTLY as they were set on thefailed ESM FRU.

Figure 87. Power Switches, Power Cords, and SCSI Interface Cables


10. Install the new ESM FRU (Figure 88).

Set the new ESM FRU into the empty slot, slide it all the way into the drivemodule and lock both handles in place.

11. Re-connect the SCSI cables (Figure 87 on page 172).

Make sure that all the cables are plugged in securely in their original locations.Attention: Connecting the cables incorrectly could cause data loss.

12. Turn on the power and check the system status.

Turn on both power switches and check the LEDs on the drive module. Thegreen LEDs should be on and the amber LEDs should be off.

If an amber LED turned on, go to “Drive Module Troubleshooting Chart” onpage 198 for instructions. If the amber LEDs remain off, but you still haveproblems with the SCSI bus transmissions to and from the disk array, it mayindicate a failed mid-plane (see “Replace a Failed MidPlane”).

13. If applicable, replace the panels (or close the doors) on the front and back ofthe cabinet.

Replace a Failed MidPlane

Problem Indicators

There may be a problem with the mid-plane if one or more of the following occur:

v Intermittent faults occur or all LEDs unlit on the drive module FRUs

v Intermittent or no I/O activity is reaching the drive module drives


Figure 88. Removing/Installing an ESM FRU


Tools/Equipment

The replacement Drive Module chassis, Phillips head screwdriver, hex nut driver,and grounding strap (or other antistatic protection device).

Instructions

Use this procedure to replace a failed mid-plane.

The mid-plane is part of the Drive Module chassis. Because the entire chassis mustbe replaced when the mid-plane fails, make sure that you exhaust all othertroubleshooting methods before you attempt this procedure. Procedures to tryinclude:

v Checking the drive module for other hardware failures

v Replacing all applicable FRUs or components (cables, drives, or ESM board)

v Checking the host adapters, SCSI bus, and software (operating system and hostRAID management tools) for problems

Remove the Drive Module1. If applicable, open the panels (or doors) on the front and back of the cabinet to

gain access to the drive module.

2. Shut down the drive module (Figure 89 on page 175).

If applicable, stop all I/O activity to the drive module and logically disconnectthe drives from the host. Turn off both power switches and unplug both powercords from the drive module. All LEDs should be off. Attention: Electrostaticdischarge can damage sensitive components. Use a grounding wrist strap orother antistatic precautions before removing or handling any drive modulecomponents.

3. Put on a grounding strap.

4. Disconnect the cables (Figure 89 on page 175).

Unplug the interface cables. The drive modules may have up to two SCSIcables. You should label each SCSI cable with the appropriate bus number.Attention: Reconnecting SCSI cables incorrectly on an ESM FRU couldcause data loss.


5. Remove all FRUs. (Figure 90 and Figure 91 on page 176).

Remove the drives, fans, power supplies, and ESM FRU. Attention: Makesure that you keep the drives in sequential order. You must replace the driveFRUs in the EXACT location from which you removed them.

Figure 89. Power Switches, Power Cords, and SCSI Cables

Figure 90. Removing/Installing Power Supplies and Interface FRUs


Attention: Do not remove the screws from just below the drive module bezel onthe front of the Drive Module (Figure 93 on page 177). These screws hold thedevice module support rails to the cabinet rails.

6. Remove the drive module from the cabinet (Figure 93 on page 177).

Do the following:

a. Remove the two screws from the back of the drive module chassis thatsecure the drive module to the support rails (see Figure 92 on page 177).

Figure 91. Removing/Installing Drive and Fan FRUs


b. Remove the screws on each side of the drive module that secure the bezeland drive module to the rack. Slide the chassis out of the cabinet and set itout on a dry, level surface.

7. Unpack the new Drive Module chassis and set it out on a dry, level surface.

Figure 92. Rear Mounting Screws

Figure 93. Front Mounting Screws


8. Install and secure the chassis into the cabinet, replace all the FRUs, andreconnect the interface and power cables. Make sure that you replace all drivesto their correct location and that you connect the cables securely in their originallocations.

Attention: Connecting the cables incorrectly to an ESM FRU could cause dataloss.

9. Turn on the power and check the system status.

Turn on both power switches and wait for the drives to spin-up. During this time,you may see the green and amber LEDs turn on and off intermittently.

Once the drives spin-up, the Power/Fault LEDs on the front panel and all PowerLEDs on the back should glow green. If so, go on to Step 10. If any Power/FaultLEDs turn amber or any Fault LEDs on the back come on, go to “Drive ModuleTroubleshooting Chart” on page 198 for instructions.


Use the Fibre Channel Storage Manager host software to verify the drivemodule’s status.


Chapter 12. Servicing the Power System

This chapter contains instructions for servicing the power supply FRUs in the DriveModule.

Power System Overview

The drive module’s power system includes the following elements:

v Two external AC power cords (one for each power supply)

v Two DC power supplies

For detailed information about the power supply FRUs, refer to “Power SupplyFRUs” on page 149.

Power Supply Servicing Notes

The drive module contains redundant power supplies that support hot swapping.This means you can replace a failed power supply while the drive module is turnedon and running. The second power supply will maintain electrical power to the drivemodule during the replacement procedure.

Power Supply Recovery Notes

Both power supplies have a built-in sensors that detect the following conditions:

v Too much voltage to the power supply

v Short circuit in one of the other FRUs

v Overheating of power supply

If one of these conditions occur, one or both power supplies will automatically lockin a shutdown mode. This means that all power remains off until you cycle thepower switches (turn the power switches off and then on again).

A power supply shutdown indicates a serious problem with the drive moduleor one of its components. You should find and correct this problem immediately.

Power Supply Temperature Sensor

There is a temperature sensor in each power supply designed to prevent them fromoverheating. If one of these sensors detects an over-temperature condition (ambientair temperature of 70° C [158° F] or above), the “overheated” power supply willautomatically shut down. The other power supply will remain on as long as itstemperature remains below 70° C (158° F). If not, the second power supply will shutdown, which turns off all power to the drive module.

Attention: There is a serious problem if the air temperature inside the cabinet ishot enough to cause the power supplies to shut down.

Once you cool the air temperature to below 70° C (158° F), you can restart thepower supplies (turn the power switches off, then on). This will cause the arraycontroller to restart itself, attempt to spin up the drives, and return to a normaloperating state. Typically, you will not need to perform additional recoveryprocedures after a power supply shutdown and restart.


Maintaining the Power System

The power supply FRUs have ″hot swap″ capability. They do not require preventivemaintenance.

Types of Power System Problems

Power problems include any malfunctions that delay or interrupt power distributionto the drive module and its components. This includes both external and internalpower problems such as power outages or a failure of the power connections to thedrive module’s midplane. All power system failures are caused by some type ofhardware problem, either in the incoming power lines, the building’s wiring, thecabinet’s electrical system, or in the drive module circuitry. Some electricalproblems are difficult to trace, especially if it involves complex site wiring in a largefacility.

You can use several tools to help determine the source of a power problem,including:

v Drive module LEDs

v Software error messages

v Troubleshooting chart (see “Drive Module Troubleshooting Chart” on page 198 fordetailed troubleshooting information)

Hardware-Related Problems

Problems involving the hardware components in the drive module’s power systemmight include:

v Loose or damaged connectors or power cords

v Overheated or defective power supply

v Midplane failure

v Failure of electrical circuits inside the cabinet

v Power failure in the building or other external electrical source

Recover from a Power Supply Shutdown

Problem Indicators

There may be a problem with one or both power supplies due to overheating,incorrect voltages, or other electrical failures when one or both of the followingoccurs:

v One or both power supply LEDs are off

v There is power to the other devices in the cabinet, but not to the drive module

Instructions

Use this procedure to regain normal system operation after a power supplyshutdown. For more information on the power supplies, refer to “Power SupplyFRUs” on page 149.

1. Read the information in “Power Supply Recovery Notes” on page 179.

2. If applicable, remove the panels (or open the doors) on the cabinet to gainaccess to the drive module.


3. Check the LEDs on the power supply FRUs (Figure 94).

Look at the power supply FRUs and select one of the following that matchestheir current LED status:

v Green LEDs are on and amber LEDs are off. Power supplies are workingproperly. No action required.

v One or both amber LEDs are on. Go to Step 4.

v All LEDs are off. Power switches are off or power cords are unplugged, orthere is another problem with the power system. Go to Step 5.

v Other amber LEDs are on (on front panel or other FRUs). Go to “DriveModule Troubleshooting Chart” on page 198 for further instructions.

Note: Always wait at least ten seconds between the time you turn a powerswitch off and when you turn the switch on again.

4. Turn on the power switches.

The drive module is plugged in, but one of the power supply switches is turnedoff. This causes the green LED to turn off and the amber LED to turn on. Turnon the power switch (or switches) and check the power supply for faults.

The green LEDs should turn on and the amber LEDs should go off. If thisoccurs, the drive module is ready to resume normal operation without furtheraction from you. If the amber LEDs remain on or the green LED remains off, goto “Replace a Failed Power Supply” on page 183. If one or both power suppliesfail to power-up or immediately shut down after recycling the power, go to Step5.

5. Restore power by answering the following.

Are the drive module’s power cords plugged in and power switches turned on?

Figure 94. Fault LEDs on the Back of the Drive Module

Chapter 12. Servicing the Power System 181

v Yes. Go to the next question.

v No. Plug in one or both power cords and turn on both switches.

Is there electrical power to the other devices in the cabinet?


v No. Check the rack power (see the rack power MAP in the SeascapeSolution Rack, Installation and Service Guide, IBM 2101 Model 100,SY27-7606) and external power source.

Does the current problem match one of the conditions listed below?

v Hot temperature. The air temperature at the back of the drive module is70°C [158° F] or higher. If Yes, go to Step 6. If No, go to next bullet item.

v One power supply shut down. The Power and Fault LED are off. If Yes, goto 6. If No, go to next bullet item.

v Both power supplies shut down. All power to the drive module is off, butother devices in the cabinet are still turned on and running. If Yes, go to Step7.

6. Turn off the power switches and cool the drive module.

Turn off both power switches and do whatever is necessary to cool the drivemodule. Once the air temperature is within normal range (below 40° C [104° F]),turn on the power switches and wait for the drive module to power up. Thegreen LEDs should turn on and the amber LEDs should remain of. If so, go toStep 7. If the power supplies remain off or a Fault LED turns on, it may indicatea failed power supply (see “Replace a Failed Power Supply” on page 183 ) ormidplane (see “Replace a Failed MidPlane” on page 173).

Attention: If the air temperature inside the cabinet is hot enough to cause thepower supplies to shut down (70° C [158° F] or above), there is a serious problemin the cabinet. Remove all panels from the cabinet immediately to help cool thedrive module. Then, do whatever is necessary to alleviate the over-temperatureproblem (such as shutting down the power or using external fans to cool the area).

7. Check the system for faults or damage.

Turn the power switches off, wait ten seconds, then turn them on again. Wait forthe drive module to power up, then check all the LEDs for faults. Then chooseone of the following:

v Drive module powered-up without fault. Use the Fibre Channel StorageManager host software to check the overall status of the drive module and itscomponents. If everything seems okay, go on to Step 8.

v Fault LED lit on one or both power supplies. Go to “Replace a FailedPower Supply” on page 183.

v Fault LED lit on other drive module FRUs. Go to “Drive ModuleTroubleshooting Chart” on page 198.

v Drive Module failed to power up or power supplies immediately shutdown again. See the rack power MAP in the Seascape Solution Rack,Installation and Service Guide, IBM 2101 Model 100, SY27-7606 .

8. If applicable, replace the panels (or doors) on the cabinet.


Replace a Failed Power Supply

Problem Indicators

There may be a problem with a power supply when one or more of the followingoccur:

v Amber Fault LED on power supply FRU is lit

v Software reports a power supply error

Note: A glowing amber LED on a power supply does not necessarilyindicate a hardware failure. If both power supplies are running andyou turn off one of the power switches, the green LED on that FRUwill go off and its amber LED will turn on. When you turn on thepower again, the amber LED will turn off and the green LED will turnon again.

Tools/Equipment

Replacement power supply FRU

Instructions

Use this procedure to replace a failed power supply.

1. If applicable, remove the panel (or open the door) on the back of the cabinet togain access to the drive module.

2. Check the LEDs on the back of the drive module (Figure 95 on page 184).

Look at the power supply FRUs and select one of the following that matchestheir current LED status:

v Green LEDs are on and amber LEDs are off. Power supplies are workingproperly. No action required. End of procedure.

v One or both amber LEDs are on. Go to Step 3 on page 184.

v All LEDs are off. Go to Step 4 on page 185.

v Other amber LEDs are lit (on front panel or other FRUs). Go to the “DriveModule Troubleshooting Chart” on page 198 for further instructions.


Note: Always wait at least ten seconds between the time you turn a powerswitch off and when you turn the switch on again.

3. Turn on the power switches (Figure 96 on page 185).

The drive module is plugged in, but one of the power supply switches is turnedoff. This causes the green LED to turn off and the amber LED to turn on. Turnon the power switch (or switches) and check the power supply for faults. Thegreen LEDs should turn on and the amber LEDs should go off. If this occurs,the drive module is ready to resume normal operation without further actionfrom you. If the amber LEDs remain on or the green LED remains off, go toStep 5 on page 185.



4. Restore power. Answer the following:

Are all LEDs on the power supplies turned off, the power cords plugged intoboth power supplies, and the power switches turned on?


v No. Plug in the cords, turn on both power supplies, and check the powersupply for faults. If the green LEDs turn on and the amber LEDs remain off,return to normal operation. If one or both of the power supply amber LEDsturn on, go to Step 5. If another fault LED on the drive module turns on, goto “Drive Module Troubleshooting Chart” on page 198.

Is there power to other devices in the cabinet, room, and/or building?

v Yes. Go to “Recover from a Power Supply Shutdown” on page 180.

v No. Go to “Restore Power After an Emergency” on page 156.

5. Read the yellow “Caution” label on the back of the drive module (between thepower supply FRUs).

6. Turn off the power and unplug the cord from the failed power supply(Figure 96).

Two glowing LEDs (green and amber) on a power supply indicates that it hasfailed. Make sure you turn off the power switch and unplug the power cordfrom the AC outlet and from the failed power supply FRU .

7. Remove the failed power supply (Figure 97 on page 186).

8. Prepare the new power supply (Figure 97 on page 186).

a. Unpack the new power supply from the packing material.

b. Make sure that the power switch is turned off.

c. Open the lever and compare it to the lever on the failed power supply. Ifboth levers opened in the same direction, go to Step 9 on page 186. If theyopened in the opposite direction, remove the lever on the new powersupply FRU and put it on the other side of the FRU.

Note:

Figure 96. Power Switches and Power Cords


v Before you install a power supply FRU, make sure that its powerswitch is turned off.

v The power supplies are interchangeable and have reversible left and rightlevers. You can insert a power supply into either slot as long as you makesure that the lever opens in the correct direction. The lever on the leftpower supply opens to the right; the lever on the right power supply opensto the left.

9. Install the new power supply FRU (Figure 97).

With the lever open and facing you (LEDs on the right), slide the new powersupply all the way into the empty slot and close the lever until it locks in place.

10. Plug in the power cord and turn on the power (Figure 96 on page 185).

11. Check the drive module LEDs for faults (Figure 95 on page 184).

After you turn on the power, the green LED on the power supply should beglowing. If so, close the cabinet panels or doors (if applicable). If the amberLED comes on or the drive module will not power-up, turn off the powerswitches and make sure that both FRUs are inserted and locked in place. Waitat least ten seconds, then turn on the power and check the LEDs. If the amberLEDs remain on or the drive module will not power-up, it probably means thatthe midplane has failed (see “Replace a Failed MidPlane” on page 173).

Figure 97. Removing/Installing a Power Supply FRU


Chapter 13. Servicing the Cooling System

This chapter contains instructions for servicing the fan FRUs in the Drive Module.

Cooling System Overview

The system’s cooling system includes the following elements:

v Two fan FRUs

v Ventilation holes in the drive FRU levers and fan FRU casing

The fan FRUs have ″hot swap″ capability, and do not require preventivemaintenance. The fans help maintain proper air circulation across the componentsinside the drive module. The ventilation holes provide air flow access to the drivemodule’s chassis. Air flows through the drive module from the front to the back. Fordetailed information about the fan FRUs, refer to “Fan FRUs” on page 151.

Fan Servicing Notes

Here are a few things to consider when replacing a failed fan:

v Do not run the drive module without adequate ventilation and cooling because itwill cause damage to the internal components and circuitry.

v You can Hot Swap a fan FRU (replace it while the drive module is turned on andrunning), as long as you complete the exchange within 15 minutes . This timelimit applies only to the total time that the fan is out of the chassis, beginningwhen you remove the failed unit and ending when you re-seat the new one. Thisdoes not include the time it takes you to perform this entire procedure (checkingLEDs, unpacking the new FRU, etcetera).

v The fan FRUs are interchangeable. You can install a new fan FRU in either fanslot as long as you turn the FRU in the correct orientation. When facing the backof the drive module, notice that the left fan FRU installs with the air vents at thetop and the latch at the bottom. The right fan installs with the latch at the top andvents at the bottom.

The procedure in this section explains how to replace a failed fan FRU. Foradditional troubleshooting information for the drive module, refer to the “DriveModule Troubleshooting Chart” on page 198.

Maintaining the Cooling Fans

Cooling problems include any malfunctions or obstructions that impede air flow, orchanges in the ambient air temperature around the drive module that cause one ormore components in the drive module to overheat. To avoid cooling problems,always keep the air vents free of obstructions. Also, make sure that the ambient airtemperature around the drive module is within environmental requirements listedunder “Heating and Air Conditioning” on page 38.


Replace a Failed Fan

Problem Indicators

There may be a problem with a fan when one or more of the following occur:

v Amber LED on fan FRU is on

v Fan motors are not running

v Amber Over-Temp LED is lit on the ESM FRU

v Software reports a fan error or over-temperature condition

Tools/Equipment

Replacement fan FRU

Instructions

Use this procedure to replace a failed fan.

1. If applicable, remove the panel (or open the door) on the back of the cabinet togain access to the drive module.

2. Check the LEDs on the back of the drive module (Figure 98 on page 189).

Look at the LEDs on the fan FRUs, power supply FRUs, and ESM FRU, thenselect one of the following:

v Amber LED on one fan is lit . Go to Step 5 on page 189.

v Amber LEDs on both fans are lit . Go to Step 3 on page 189.

v Amber LED on ESM FRU is lit . Go to Step 4 on page 189.

v One (or both) amber LEDs on power supplies is on . Go to “Replace aFailed Power Supply” on page 183.

v No amber LEDs are lit on the back of the drive module , yet software isreporting an over-temperature condition. Go to Step 4 on page 189.


3. Shut down the drive module immediately.

Do not run the drive module if both fan FRUs have failed. Stop all activity to thedrive module and turn off both power switches. Go to Step 5.

4. Answer the following questions.

Can you hear the motors running in both fan FRUs?


v No. Place your hand in front of both sets of air vents on each fan FRU andsee if you can feel air blowing against your hand. If you can feel air exitingthrough both sets of vents, the fan FRUs are probably working correctly.Answer the next question. If you cannot feel air exiting through one or morevents on either fan FRU, go to Step 5.

Is the Fault LED on the ESM FRU lit?

v Yes. This indicates that the ambient air temperature may have risen above(40°C [104°F]). Check the air temperature around the drive module. If it is toohot, take necessary steps to cool the area around the drive module. If thetemperature is within the required operating range, there may be a defectiveLED on the ESM FRU. Go to “Replace a Failed ESM FRU” on page 170.

v No. If the operating system or host software is reporting a fan or over-temperror, yet you cannot detect a problem, the ESM board or midplane may bemalfunctioning. Go to “Replace a Failed ESM FRU” on page 170.

5. Unpack the replacement fan FRU.

6. Remove the failed fan FRU (Figure 99 on page 190).


Chapter 13. Servicing the Cooling System 189

7. Install the new fan FRU (Figure 99).

Using Figure 99 as a guide, make sure that you are holding the new fan FRU inthe correct position. For the left fan, hold the FRU with vents up and handledown. For the right fan, hold the FRU with handle up and vents down.

Note: If you turned the power off in Step 3 on page 189, the LED on the newfan FRU will not turn on when you insert the FRU.

8. Check the LEDs again (Figure 98 on page 189).

If applicable, turn on the power switches. The Fault LED on the fan FRU shouldturn off after a few seconds. If Fault LED remains on, make sure that the FRUis inserted correctly and locked in place. If it is, but the Fault LED remains on,the fan may be defective. Replace it with another fan FRU. If replacing the fandoes not solve the problem, the drive module’s midplane may have failed (see“Replace a Failed MidPlane” on page 173).

9. Replace the cabinet panel or close the back door, as necessary.

Figure 99. Removing/Installing a Fan FRU


Chapter 14. Technical Reference

This chapter contains specifications and other technical information about the DriveModule.

Technical Specifications

Factory Settings

Prior to shipping, the factory sets the drive module hardware switches as shown inTable 35.

Table 35. Factory Hardware Settings

Switches Explanation See:

PowerPower Settin g = 0 (Off) . Two switches (one per power supply) thatturn the power supplies on (switch at 1) and off (switch at 0).

“About the Power System” onpage 149

ESM FRU Switches

Tray IDTray ID Setting = 0. Binary-coded digital (BCD), rotary DIP switchsets the drive module’s tray ID numbers 0 through 9.

“Environmental Services MonitorBoard” on page 146

OptionSwitches

Five switches that set drive interface options. “Environmental Services MonitorBoard” on page 146

Switch 1: Bridge Disable (SCSI IDs 5, 6, 7, and 0xD are not used)

On = causes two independent, 5-drive buses with oneconnection to each bus, and the drive IDs are number 0-4for bus 1 and 0-4 for bus 2, and one SAF-TE chipnumbered 0xF.

Off = causes one 10-drive bus with two connectors to the bus,and the drives to that bus will be numbered 0-4 and 8-0xC,and the SAF-TE chips will be numbered 0xE and 0xF.

Step 5 of “Installing the DriveModule” on page 49.

Switch 2: SAF-TE Chip Disable (Default is Off)

Off = all SAF-TE chip functions operate as required

On = no SAF-TE chip services

Switch 3: Power Off Bus Reset Enable (Default is Off)

Off = disabled: deactivates this feature

On = enabled: causes a reset for both SCSI buses if bothPWRFLT signals are detected

Switch 4: UPS support (Default is Off)

Off = disables: no UPS support to the drive module

On = enables: allows UPS support, and the host perform acache memory dump to the drive module during a poweroutage

Switch 5: This switch is reserved. It has no function at this time.


Hardware Features

Table 36 lists some of the features you will find in the drive module.

Table 36. Drive Module Features

Features Elements Descriptions

General

ModularizedComponents

High-capacity disk drives

Environmental Services Monitor (ESM) board

Power supplies

Cooling fans

Technology Supports disk array technology and RAID levels 0, 1, 3, and 5 through aSCSI host interface

Redundant data storage, cooling system, and power system

Hot swap logic for drive, power supply, and fan FRUs

Automatic recovery after power failure without user intervention

User Interface Built-in Power, Active, and Fault indicators

Labeling on rear FRUs, indicator lights, switches, and connectors

Easy-to-replace drive, ESM, power supply, and fan FRUs

Disk DriveStorage

Current Capacities

Storage per drive FRU: 4.5, 9 and 18 GB

Maximum drives per drive module: 10

Maximum storage per drive module: 180 GB

5 or 10 drives per drive channel (set by Bridge Disable switch)

1 or 2 drive channels per drive module (set by Bridge Disable switch)

ESM Board

ID Numbers

Drive channel numbers: 1 and 2

Drive SCSI IDs: 0, 1, 2, 3, 4 for each 5-drive bus (if configured as two 5-drivebuses) Drive SCSI IDs: 0, 1, 2, 3, 4 and 8, 9, A, B, C (if configured as one10-drive bus)

Tray IDs: 0 to 9 (ESM board host side)

Interfaces SCSI, multimode LVD/SE

SCSI bus interface: Two, 68 pin, VHDCI connectors for SCSI bus cables thatallows for a choice of two drive configurations

Software Features

Through the host interface, this drive module supports Fibre Channel StorageManager software, an application used to configure and manage disk arrays. FibreChannel Storage Manager provides configuration tools that allow you to define thephysical and logical space on each drive in preparation for data storage. Whether ornot you need to configure the drive module depends on several factors, such as:

v How many drives are installed in the drive module

v How and where the drive module is connected to the SCSI bus

v What type of host and operating system you are using with the drive module

v What type of RAID management software you are using on the drive module

v Whether or not you want to use the factory default configuration settings (numberof LUNs, RAID level, hot spare drives, etc.)


Table 37 lists a few of the default software parameters that may or may not be setat the factory prior to shipment. Before you attempt to store data on the drivemodule, you should use Fibre Channel Storage Manager or the appropriatesoftware to determine the following:

v Exactly how the drive module is currently configured

v Whether or not you want to change that configuration

Table 37. Sample Disk Array Software Parameter Settings

Parameter Explanation

RAID Level Defines how data is stored on the logical units (LUNs) and whether or not there isdata redundancy, based on a RAID level. There are four RAID levels: 0, 1, 3, and5. RAID levels 1, 3, and 5 offer data redundancy.

Drive Group Defines which physical drives make up each logical unit.

Caching Determines whether data will be stored in cache memory. This is specified on alogical unit basis.

Segment Size Defines the amount of data (segment size) a controller will write to a single drive ina logical unit, before writing data to the next drive. Segment sizes are determinedby the total number of data blocks.

Reconstruction Rate Determines the total number of data blocks the controller will reconstruct duringone reconstruction operation. Defines the amount of time (delay interval) betweeneach reconstruction operation.

Note: Depending on the operating system, host RAID management software, andhost devices in your system, the drive module may be referred to as a diskarray, a RAID module, a drive drawer or other type of unit. Keep thisterminology in mind when using any configuration software. For moreinformation about software configuration and operating instructions, refer tothe Fibre Channel Storage Manager or operating system softwaredocumentation.

Interface Connections and Cables

Drive Module Interface Connections

The interface to the drive module is a SCSI interface, which is the primaryconnection to the hosts and other devices on the SCSI bus.

The SCSI interface protocols and cables allow you to connect the drive module toone or two hosts. You can customize the drive module’s interface connections tomatch the host and networking requirements at the site. The following sectionsprovide detailed information regarding the interface, cabling requirements, and otherthings you should know regarding drive module installation requirements.

Host SCSI Interface Connections

The drive module supports 16-bit, multimode low voltage differential (LVD), hostSCSI-3 interfaces. This host interface provides a common link between an LVD hostand SE SCSI drive modules. If you intend to install the drive module on a SCSIbus, you will use the 68-pin, VHDCI, SCSI interface connectors provided on theback of the unit. Each connector is terminated internally, therefore, the drive moduleis intended to be connected at the end of the SCSI bus. For information on:

v SCSI cables, refer to “SCSI Cables” on page 194

Chapter 14. Technical Reference 193

v SCSI cable pin assignments, refer to “Host SCSI Pin Assignments and Signals”

SCSI Cables

The maximum length for an LVD SCSI cable is 12 m (39 ft.) for 32 AWG(0.0324mm²), and 25 m (82 ft.) for 28 AWG (0.08042mm²). The total lengthincludes both internal and external cabling. The SCSI cabling inside this drivemodule is approximately 0.1 m (4 in.) for the host bus. The maximum length for anySE SCSI bus shall not exceed 3 m (9.8 ft.). Table 15 lists the SCSI cable that youcan use on this drive module.

Host SCSI Pin Assignments and Signals

Table 38 lists the host SCSI interface pin assignments for the multimode LVDVHDCI cable connections. Table 39 describes each SCSI signal.

Table 38. SCSI Pin Assignments for Multimode LVD (VHDCI) Cable

Pin Signal Pin Signal Pin Signal Pin Signal

1 +DB(12)* 18 TERMPWR 35 -DB(12) 52 TERMPWR

2 +DB(13)* 19 RESERVED 36 -DB(13) 53 RESERVED

3 +DB(14)* 20 GROUND 37 -DB(14) 54 GROUND

4 +DB(15)* 21 +ATN* 38 -DB(15) 55 -ATN

5 +DB(P1)* 22 GROUND 39 -DB(P1) 56 GROUND

6 +DB(0)* 23 +BSY * 40 -DB(0) 57 -BSY

7 +DB(1)* 24 +ACK* 41 -DB(1) 58 -ACK

8 +DB(2)* 25 +RST * 42 -DB(2) 59 -RST

9 +DB(3)* 26 +MSG * 43 -DB(3) 60 -MSG

10 +DB(4)* 27 +SEL * 44 -DB(4) 61 -SEL

11 +DB(5)* 28 +C/D * 45 -DB(5) 62 -C/D

12 +DB(6)* 29 +REQ * 46 -DB(6) 63 -REQ

13 +DB(7)* 30 +I/O * 47 -DB(7) 64 -I/O

14 +DB(P)* 31 +DB(8)* 48 -DB(P) 65 -DB(8)

15 GROUND 32 +DB(9)* 49 GROUND 66 -DB(9)

16 DIFFSENS 33 +DB(10)* 50 GROUND 67 -DB(10)

17 TERMPWR 34 +DB(11)* 51 TERMPWR 68 -DB(11)

Note: An asterisks (*) Denotes GROUND when operating in multimode SE (MSE) mode.

Table 39. Host SCSI Signal Descriptions

Signal Name Description

BSY BUSY An “or-tied” signal indicating that the bus is being used.

SEL SELECT A signal used by an Initiator to select a Target or by a Target tore-select an Initiator.

C/D COMMAND/DATA A signal driven by a Target indicating whether CONTROL or DATAinformation is on the data bus. True indicates CONTROL.

I/O INPUT/OUTPUT A signal driven by a Target controlling the direction of datamovement on the data bus with respect to the Initiator. Trueindicates input to the Initiator.


Table 39. Host SCSI Signal Descriptions (continued)


MSG MESSAGE A signal driven by the Target during a MESSAGE phase.

REQ REQUEST A signal driven by the Target to indicate a request for an REQ/ACKdata transfer handshake.

ACK ACKNOWLEDGE A signal driven by the Initiator to indicate acknowledgment for anREQ/ACK data transfer handshake.

ATN ATTENTION A signal driven by the Initiator indicating an ATTENTION condition.

RST RESET An “or-tied” signal indicating the RESET condition.

DIFFSENS DIFFERENTIAL SENSE A signal indicating if the bus is LVD, SE, or differential.

DB(0-15,P,P1) DATA BUS, PARITY Sixteen-bit data bus with odd parity used for data transfer andBUS DEVICE ID during ARBITRATION

SCSI Drive Pin Assignments and Signals

Table 40 lists the SCA-2 interface pin assignments for the SCSI disk drives.Table 41 describes each SCSI signal.

Table 40. SCA-2 Interface Pin Assignments

Pin Signal Pin Signal Pin Signal Pin Signal

1 +12 V charge 21 -DB(7) 41 GROUND 61 +DB(7)*

2 +12 V 22 -DB(6) 42 GROUND 62 +DB(6)*

3 +12 V 23 -DB(5) 43 GROUND 63 +DB(5)*

4 +12 V 24 -DB(4) 44 Mated 1 64 +DB(4)*

5 NC (Opt. 3.3 V) 25 -DB(3) 45 NC (Opt. 3.3 Vcharge)

65 +DB(3)*

6 NC (Opt. 3.3 V) 26 -DB(2) 46 DIFFSENSE* 66 +DB(2)*

7 -DB(11) 27 -DB(1) 47 +DB(11)* 67 +DB(1)*

8 -DB(10) 28 -DB(0) 48 +DB(10)* 68 +DB(0)*

9 -DB(9) 29 -DB(P1) 49 +DB(9)* 69 +DB(P1)*

10 -DB(8) 30 -DB(15) 50 +DB(8)* 70 +DB(15)*

11 -I/O 31 -DB(14) 51 +I/O* 71 +DB(14)*

12 -REQ 32 -DB(13) 52 +REQ* 72 +DB(13)*

13 -C/D 33 -DB(12) 53 +C/D* 73 +DB(12)*

14 -SEL 34 +5 V 54 +SEL* 74 Mated 2

15 -MSG 35 +5 V 55 +MSG* 75 GROUND

16 -RST 36 +5 V charge 56 +RST* 76 GROUND

17 -ACK 37 SPINDL SYNC + 57 +ACK* 77 ACTIVE_LED

18 -BSY 38 RMT_START 58 +BSY* 78 DLYD_START

19 -ATN 39 SCSI ID0 + 59 +ATN* 79 SCSI ID1 +

20 -DB(P) 40 SCSI ID2 + 60 +DPP* 80 SCSI ID3 +

Table 41. Drive SCSI Signal Descriptions


+12 V +12 V power Power supply voltage for the drives.

Chapter 14. Technical Reference 195

Table 41. Drive SCSI Signal Descriptions (continued)


+12 V charge +12 V pre-charge A +12 V pre-charge for “hot plugging” the drives.

+5 V +5 V power Power supply voltage for the drives.

+5 V charge +5 V pre-charge A +5 V pre-charge for “hot plugging” the drives.

Mated 1/2 In place lines Signals used to determine when the drive is in place. Mated 1connects to Mated 2 on the midplane. Mated 2 is ground for thedrive and can be used as the “drive in place” signal.

SYNC + SYNC Spindle Not used by this drive module. A signal used to synchronizespindles between multiple drives.

RMT_START Remote Start A signal that specifies whether or not the drive must wait for acommand from the host controller before performing SCSI spin-up.A low signal means wait for the spin-up command.

DLYD_START Delayed Start When the RM_START signal is high, this signal specifies whetheror not the drive must delay spin-up based on its SCSI ID. If thissignal is high, the drive will spin-up as soon as power is applied. Ifthis signal is low, the drive will delay spin-up after power is appliedfor nn seconds (12 seconds x drive SCSI = nn seconds). If theRM-START signal is low, the DLYD_START signal has no effect onthe drive spin-up.

SCSI_ID0-3 SCSI ID Signals used to specify the drive SCSI ID.

ACTIVE_LED Active LED driver A signal used to activate a remote Active LED that specifies whenthe drive is active.

BSY BUSY An “or-tied” signal indicating that the bus is being used.

SEL SELECT A signal used by an Initiator to select a Target or by a Target tore-select an Initiator.

C/D COMMAND/DATA A signal driven by a Target indicated whether CONTROL or DATAinformation is on the data bus. True indicates CONTROL.

I/O INPUT/OUTPUT A signal driven by a Target controlling the direction of datamovement on the data bus with respect to the Initiator. Trueindicates input to the Initiator.


Chapter 15. Quick References

Drive Module PartsTable 42. Parts on a Drive Module

Component Parts Setting Function

Front Panel

Active LED Green Glows intermittently during drive I/O operations

Blinks to indicate a drive identification command to thedrive

Power/Fault LED Green Glows when there is power to the drive

Amber Glows to indicate a drive failure

Drive FRUs Lever Handle and lock for the drive FRUs

ESM FRU

SCSI Connectors Provide SCSI bus connections to host controllers

Option Switches On or Off Select the drive options (set of five switches)

Tray Switch 0 through 9 Selects the drive module’s tray ID number

Over Temp LED Amber Glows during an over-temperature condition

Power LED Green Glows when there is power to the ESM board

TERM Power Green One for each connector:

v Glows when TERM Power supplied by the connectedhost is detected

v Glows whether or not either AC power cord isconnected

Bus Activity Green One for each connection:

v Glows when TERMPPWR is detected on the bus, butthere is no activity

v Blinks when a drive is in use

v Off when drive not in use

Bus Mode (LVD/SE) Green One for each connection:

v Glows green for LVD connection

v Off for SE connection

Lever Handle and lock for the ESM board

Fan FRUs Fault LED Amber Glows after a fan failure

Power SupplyFRUs

Power LED Green Glows when the power is on

Fault LED Amber Glows when one Power switch is turned off or powercord is unplugged, after a power supply failure, or whenthe power supply malfunctions

Lever Locks and unlocks the power supply FRU

AC Connector Provides an AC connection to the power source

AC Power Switch 0 or 1 Turns the power on and off to the power supply


Drive Module Troubleshooting ChartTable 43. Drive Module Troubleshooting Chart

Component Problem Possible Cause Possible Solution See:

Front panelLEDs above oneor more drives

Amber LED on, greenLED off

Glowing amber: Drivefailure

Replace failed drive FRU. “Replace aFailed Drive” onpage 160

Both LEDs off above1 or more drives, butLEDs above otherdrives in the drawerare on

Drive slot empty or FRU notplugged in

Make sure that the driveFRU is inserted and lockedin place correctly. If youremove a drive FRU fromits slot, always wait at least10 seconds before you plugit back into the drivemodule.

“Maintaining theDrives” onpage 160

Drive failure If drive FRU is locked inplace and its Power/FaultLED remains off, replacethe drive.

“Replace aFailed Drive” onpage 160

Green LEDs offDrives on same SCSIbus.

No activity to the drives No action required. n/a

Damaged or loose SCSIcables

Check SCSI bus cablesand connections.

“Hints forTroubleshootingInterfaceProblems” onpage 169

ESM board failurev Use host RAID

management software tocheck the SCSI busstatus.

v Try sending an “identifydrive” command to theaffected drive or drives,causing Power/Fault LEDto blink amber/green.

v Replace the ESM board.

“Replace aFailed ESMFRU” onpage 170

Midplane failure Replace midplane. “Replace aFailed MidPlane”on page 173


Table 43. Drive Module Troubleshooting Chart (continued)


Front panel (allLEDs)

Green LEDs on,amber LEDs off

Glowing power and blinkingactivity LEDs: Normal driveactivity.

No action required. n/a

ALL LEDs off Drive module power offv Check that both drive

module power cords areplugged in and bothpower switches are on.

v If applicable, check thatthe cabinet’s main circuitbreakers are turned on.

“Turn On thePower” onpage 153

AC power failure. Check building’s circuitbreaker and AC outlet.

n/a

Power supplies failed. Replace both powersupplies.

“Replace aFailed PowerSupply” onpage 183

Midplane failure. Replace failed midplane. “Replace aFailed MidPlane”on page 173

ESM board failure. Replace failed ESM board. “Replace aFailed ESMFRU” onpage 170

Drives and SCSIbus

Unable to accessdrives on one or bothSCSI buses

SCSI cabling

Make sure SCSI cables areundamaged and properlyconnected.


ESM board failure Replace failed ESM board. “Replace aFailed ESMFRU” onpage 170

Chapter 15. Quick References 199



ESM FRU

Power LED on, amberLED off

Normal operationNo action required. n/a

Power LED on, amberLED on

Drive module is overheated Check fans for faults andmake sure motors arerunning. Replace failed fanif necessary.

“Replace aFailed Fan” onpage 188

Environment too hot Check the ambienttemperature around thedrive module. Cool asnecessary.

n/a

Defective LED or hardwarefailure v If you cannot detect a

fan failure or overheatingproblem, replace ESMboard.

v If replacing the ESMdoesn’t solve theproblem, replace themidplane.

“Replace aFailed ESMFRU” onpage 170 or“Replace aFailed MidPlane”on page 173

Term Power offHost not connected orturned on

Check connections to host,and that power is on.

n/a

Active Power offHost not communicatingwith drives

Check connections to host. n/a

LVD/SE off for LVD

Host either not connected,not in LVD mode, or a SEcomponent is on the bus.

v Check connections tohost; confirm LVDsettings on for LVD

v Remove SE componentfrom bus

n/a

LVD/SE on for SEHost

Host in LVD mode or ESMboard is faulty

v Confirm LVD settings onhost

v check for faulty ESMboard


Fan FRU

Amber LED off Normal operation No action required. n/a

Amber LED on and/orfan motor stopped

Fan failure Replace failed fan FRU. “Replace aFailed Fan” onpage 188




Power SupplyFRU

All LEDs off

Both power cordsunplugged or switchesturned off

v If necessary, plug in thepower cords.

v Turn on power switches.


LEDs on one FRU areoff

Power supply not pluggedin properly v Turn off the power

switch.

v Make sure the powersupply is plugged inproperly and locked inplace.

v Turn the power on again.

See Figure 97on page 186

Green LEDs on,amber LEDs off

Both power cords pluggedin and switches turned on

No action required. n/a

Green LEDs off,amber LED on

One power supply isplugged in and turned on,the second isn’t

v If necessary, plug in thepower cord.

v Turn on the powerswitch.


Power failure in building orroom v Turn off both power

switches.

v Wait at least 10 seconds,then turn on the poweragain.

v Check the drive modulefor faults.

“Restore PowerAfter anEmergency” onpage 156 and“Checking theDrive Module”on page 156

Power supply failure Replace failed powersupply.


All FRUs All green LEDs off

Drive module power off

v Check that both drivemodule power cords areplugged in and bothpower switches are on.

v If applicable, check thatthe cabinet’s main circuitbreakers are turned on.


AC power failure Check building’s circuitbreaker and AC outlet.

n/a

Power supplies failed Replace both powersupplies.


Midplane failure Replace failed midplane. “Replace aFailed MidPlane”on page 173

Chapter 15. Quick References 201

Part 5. Debugging Tools and Procedures


Chapter 16. RAID Manager for DOS

This section describes the RAID Manager for DOS utility.

Attention: RAID Manager for DOS provides many options beyond those describedin the following sections. Many of these options can cause significant harm to thedisk array if used improperly. Only use the functions described in this document orunder the supervision of your next level of support.

What is RAID Manager for DOS?

RAID Manager for DOS (DRM) is made up of a pair of DOS-based programs thatcan be used to maintain the array. With DRM, you can perform disk arrayoperations independently of your host operating system. DRM requires no specialsoftware for the operating system to use the disk array.

The two programs that make up DRM are:

v RAID Manager for DOS Main Program (drm.exe) - this program contains menusand options that can be used to maintain the disk array subsystem. Many of themenu options provide advanced functions that should only be used under thedirection of your next level of support.

v Array Configuration Editor (ace.exe) - this program contains options to viewand change the status of logical units and drives in the disk array subsystem.This program also contains many advanced functions for configuring the array,formatting drives, etc. that should only be used under the direction of your nextlevel of support. You can access this program from within the RAID Manager forDOS main program by selecting configure → Logical Units/Drives from theDRM Main menu.

DRM is shipped with the subsystem on a DOS bootable diskette. It can be run froman IBM compatible PC or laptop that is connected to the array controller via a serialcable.

When to Use RAID Manager for DOS

All the functions necessary to service and maintain the disk array are available fromthe host operating system storage management software (Fibre Channel StorageManager running on fibre channel connected hosts or StorWatch Fibre ChannelExpert running on a network connected PC) and should be accessed from therewhenever possible.

Typically, the only time you’ll need to use RAID Manager for DOS is when you needto check/verify subsystem component status and the host system running thestorage management software is remotely located or otherwise inaccessible. This isconsidered the ″normal″ case and the required procedures are described in thefollowing sections.

There may be other instances where RAID Manager for DOS can be used toisolate, resolve or recover from a problem. However, these are considered″exception″ cases and are beyond the scope of this document. These cases shouldbe handled under the direction of your next level of support.


Menu Options Summary

The table in Table 44 is a brief description of each menu item and its subsequentoptions and usage. A summary of ″normal″ tasks that are described in thisdocument is shown in Table 45 on page 208.

Important: The host operating system storage management software (FibreChannel Storage Manager running on fibre channel connected hosts orStorWatch Fibre Channel Expert running on a network connected PC)is generally more efficient for most purposes than RAID Manager forDOS. Unless you are specifically directed to this section, you shouldrefer to Fibre Channel Storage Manager and StorWatch Fibre ChannelRAID Specialist, User’s Guide, SC26-7285 for performing array tasks.

Table 44. RAID Manager for DOS Menu Items and Options.

Menu Item Option/Function Reference/Usage

Configure

v Logical Units/Drives - Starts the the ArrayConfiguration Editor (ACE) which can be used to checkthe configuration and status of logical units and drives.

See “Using the Array ConfigurationEditor (ACE)” on page 212

v Controller Name - Change the user-assigned name(ID) of the controller.

This option should only be used underthe direction of your next level ofsupport.

v Reset Configuration - Reset the controllerconfiguration.

This option should only be used underthe direction of your next level ofsupport.

Status

v Monitor Arrays - Run the Array Monitor to continuouslymonitor the array for errors.

This option should be performed usingthe host storage managementsoftware or under the direction of yournext level of support.

v Controllers - Determine what type of controller youhave in your array subsystem.

See “Identify the Controller or Changethe Name” on page 222.

v Logical Units v Drives v Other Components

Check the status of the logical units, drives and othercomponents in the array subsystem

See “Using the Array ConfigurationEditor (ACE)” on page 212.


Table 44. RAID Manager for DOS Menu Items and Options. (continued)

Menu Item Option/Function Reference/Usage

Maintenance

v Controller Pair - Service redundant controller pairs.

v Swap Passive and Active

v Fail Controller

v Reset Controller

v Change Redundant Controller Status

v Reassign LUNs to Controllers


v Parity Check And Repair - Run parity check/repair toensure array parity.


v LUN Reconstruction Parameters - Changereconstruction rate parameters to speed up or slow downreconstruction.

This option should only be used underthe direction of your next level ofsupport

v Scan For Devices - Re-scan the bus for array devices.See “Scan the Bus for Array Devices”on page 222.

v Send Controller firmware - Download new controllerfirmware.


v Receive Configuration Values v Send ConfigurationValues

Receive and send NVSRAM values

This option should only be used underthe direction of your next level ofsupport

v Caching - Set the Fast Load Cache option


v Reset the Battery Timer - Reset the date for a newlyinstalled battery. v Set Battery Age - Set battery age inunits of 90 days after upgrading controller firmware. vDisplay Battery Age - Display the battery age in units of90 days.

See “Display and Set the Battery Age”on page 226.

Diagnosticsv Controller Self Test Results - Review results of thelast controller self-test. v Data Path Test - Test the datapath to the array.

See “Diagnostics” on page 225.

Options

View Logs - View the parity and monitor logs.

The parity and monitor functionsshould be performed using the hoststorage management software orunder the direction of your next levelof support, so, under normalconditions, no parity or monitor logswill be available for viewing. If theyneed to be created and viewed, itshould be under the supervision ofyour next level of support.

Password - Change the DRM password.See “Changing the Password” onpage 226.

DOS Shell - return to DOS. This option is not used.

Chapter 16. RAID Manager for DOS 207

Task Summary

Table Table 45 is a summary of the ″normal″ tasks that can be performed usingRAID Manager for DOS.

Note: RAID Manager for DOS provides many options beyond those described inthis table and the following sections. Many of these options can causesignificant harm to the disk array if used improperly. Only use the functionsdescribed in this document or under the supervision of your next level ofsupport.

Table 45. RAID Manager for DOS Task Summary

Task When Do I need To Do It? Reference

Display Battery AgeUse this option to check the age of a battery in a RAID Module. Theage is displayed in units of 90 days.

See “Display and Setthe Battery Age” onpage 226.

Identify Drives andLogical Units

If you have multiple logical units or have more than one activecontroller and find it difficult to keep track of them.

See “Identifying Drivesand Logical Units” onpage 222.

Identify a ControllerIf you have several disk arrays installed and want to distinguish onefrom another.

See “Identify theController or Changethe Name” onpage 222.

Reset the BatteryTimer

When you install a new battery in a RAID Module, use this option toreset the battery timer to the current date.


Run Diagnostic TestsRun diagnostic tests to view the results of the last controller self-testperformed during power-up or to verify the data path between thecontroller and the array.

See “Diagnostics” onpage 225

Scan the bus for arraydevices

v If you are using DRM over a serial connection and you disconnectthe cable from one controller and attach it to another controllerwhile DRM is running. The scan detect the devices on the newcontroller.

v If DRM gives you a message that it cannot find any controllers orlogical units that you know are there. This sometimes occurs afteryou have done something to alter the configuration or confuseDRM. In this case, the scan detects these devices again.

Note: Most scans are automatic. For example, DRM scans fordevices each time you start it. Similarly, whenever you leave the theArray Configuration Editor (ACE), DRM automatically scans the arrayfor any changes you may have made to logical units while you werein ACE.

See “Scan the Bus forArray Devices” onpage 222.

Set Battery AgeThis option is used to set the battery age after upgrading controllerfirmware.


PC Requirements and Preparation Tasks

PC Requirements

The PC you connect to the individual array controllers must meet the followingrequirements:


v A 386 or higher IBM compatible PC

v At least 440 KB of available memory

v An available serial port at either COM1 or COM2

Note: Because DRM communicates over the serial interface to the disk arraysubsystem, you will experience slower response times than if you werecommunicating over a faster interface such as Fibre Channel or SCSI.

DRM displays numerous Command In Progress messages to let you knowthat operations are currently taking place. Most operations will be completedin a short amount of time (less than 1 minute).

In general, about 5 to 7 minutes is the maximum time that a given operationshould take to complete. This does not include operations such as formattinglogical units which depend on the capacity being configured. Also, theoperation that scans for devices will vary depending on the baud rate andthe number of array devices. Therefore, make sure you allow sufficient timewhen you suspect a problem before trying to abort a particular operation.

Note: Make sure that no other storage management activity is being performed onthe array subsystem (i.e. from the host or another DRM session) while youare running DRM.

Preparation Tasks

Before using DRM for the first time, perform the following preparation tasks:

1. Make a copy of the original DRM bootable program diskette.

v Use a blank, formatted high-density diskette.

v Use the DOS Diskcopy command.

v Label the duplicate diskette ″RAID Manager for DOS - Work Disk ″. This willbe the copy you will use to access the array subsystem.

2. Store the original DRM bootable diskette in a safe place.

Note: If you are making another working copy of the DRM program, but you havealready used DRM to access the array subsystem, you must be aware of thefollowing:

v If you named the controllers using the Change Controller Name option orthe the Array Configuration Editor (ACE), you will have to name themagain.

v When you access ACE for the first time, you will have to specify thephysical arrangement (layout) again.

v If you changed the default log files for monitor or parity operations you willhave to specify them again.

v If you were directed to create a batch file for the monitor operation forremote notification, you will have to specify the name of the batch file inthe drm.cfg file again.


Changing DRM Boot Up Defaults (Floppy Drive and COM Port)

By default, DRM will attempt to access the PC floppy drive as drive a: andcommunicate with the array subsystem using communications port 1 (COM1). If thePC you are using to connect to the array subsystem must access the floppy driveas b: or the serial port using COM2, then you must alter the config.sys file on theDRM diskette.

1. Insert the DRM diskette in the floppy drive.

2. Using your preferred editor, edit the config.sys file on the DRM diskette.

3. Find the following line: device=a:\drmdrvr.sys COM1

4. To modify the floppy drive designation, change the a: to b: . To use the COM2port, change COM1 to COM2. For example, if both the floppy drive designationand COM port had to be changed, the line in the config.sys should read:device=b:\drmdrvr.sys COM2.

5. Save the update config.sys file.

6. If you are changing the floppy drive designation, then edit the autoexec.bat fileon the DRM diskette.

7. Find the following line: a:drm and change the a: to b:. The line should nowread: b:drm.

8. Save the updated autoexec.bat file.

Using DRM with a Monochrome Display

By default, DRM assumes the PC being used has a color monitor. If you are usinga monochrome monitor and DRM cannot be viewed properly, then you can changethe autoexec.bat on the DRM diskette to have DRM start-up with the -m flag to usea monochrome monitor.

1. Insert the DRM diskette in the floppy drive.

2. Using your preferred editor, edit the autoexec.bat file on the DRM diskette.

3. Find the following line: [path]\drm and change it to:[path]\drm -m

where [path] is the floppy drive designation (a: or b:).

4. Save the updated autoexec.bat file.

Connecting to the Controller Locally

This section explains how to connect a local PC or laptop directly to the arraysubsystem using a serial connection.

1. Use the RAS cable (p/n 08L8045) provided with the subsystem to connect thePC to the subsystem. Attach the 9-pin connector to the appropriate controller inthe controller module. Attach the 25-pin connector to the serial port on the backof the PC. Refer to the PC and subsystem hardware manuals for additionalinformation regarding serial connectors and their locations.

2. Continue with “Starting DRM” on page 211.


Starting DRM1. Make sure the PC is connected to the array subsystem with the null modem

cable provided. See “Connecting to the Controller Locally” on page 210.

2. Make sure DRM is set up to use the appropriate monitor type, floppy drivedesignation and COM port for this PC. By default, DRM assumes a colormonitor and will attempt to access the floppy drive as a: and the serial port asCOM1.

v If you are using a monochrome display and find that DRM cannot be viewedproperly, then you can change the autoexec.bat file on the DRM diskette touse the -m flag when DRM starts. See “Using DRM with a MonochromeDisplay” on page 210.

v If the PC you are using to connect to the array subsystem must access thefloppy drive as b:, then you must alter the config.sys. and autoexec.bat fileson the DRM diskette. See “Changing DRM Boot Up Defaults (Floppy Driveand COM Port)” on page 210.

v If the PC you are using to connect to the array subsystem must access theserial port using COM2, then you must alter the config.sys file on the DRMdiskette. See “Changing DRM Boot Up Defaults (Floppy Drive and COMPort)” on page 210.

3. Insert the DRM diskette in the floppy drive and reboot the PC.

4. The program will start and present you with a password start-up box.

Notes:

a. The first time you start DRM, you will be asked to enter a password of yourchoice. The default password is RAID. If you just enter RAID for thepassword, you will be prompted for a new password each time you start theprogram. Therefore, change the password to something other than RAIDafter you first start the program.

b. You can change the password later by selecting Options → Password fromthe DRM main menu and entering the desired password.

c. If you forget your password, you will have to make another copy of youroriginal DRM diskette and use the new copy to start the program. The newcopy will have the original, default password and will prompt you for a newpassword when you first start the program. See “Preparation Tasks” onpage 209.

d. After you enter the password, DRM immediately starts scanning all attachedcontrollers for logical units.

Note: Depending on the number of devices in the system, DRM can take up toseveral minutes to complete the scan.

After the bus scan is completed, the opening screen appears with the DRMmain menu:


5. If this is the first time you have started DRM, you should verify the arraysubsystem installation and the communication paths to the DRM PC using theprocedure described in “Verifying the Installation”. Otherwise, you can nowproceed with the DRM task you wish to perform.

6. After you are finished with DRM, you should quit the program completely usingthe Quit option from the DRM main menu.

Verifying the Installation

It is a good idea to run the RAID Manager for DOS (DRM) Array Monitor after youfirst install the subsystem or start DRM because it checks all controllers, drives andother components for any problems in your array subsystem as well as verifies thecommunication paths between the controllers and the DRM PC. See “Using theArray Monitor” on page 223 for more information on the Array Monitor.

Use the following procedure to determine if there are any subsystem componentsthat are not working properly:

1. From the DRM main menu, select Status → Monitor Arrays to start the ArrayMonitor and determine if there are any subsystem components that are notworking.

2. Select all the default values from the Array Monitor start-up menus.

3. The Monitoring In Progress message and the logical unit currently beingchecked appear.

If any error occurs, note the affected component and take the appropriateaction.

4. Wait for the Waiting For Next Polling Interval message to appear (indicatingthat the monitor has scanned all the logical units).

5. Press <Q> to exit the Array Monitor.

Using the Array Configuration Editor (ACE)

The Array Configuration Editor (ACE) program provides a powerful interface into thearray subsystem. This is the primary interface that will be used to view the arrayconfiguration and status. This interface also provides many advanced features formodifying the array configuration and status, formatting and reconstructing drivesand altering cache parameters that should only be used under the direction of yournext level of support.

Figure 100. RAID Manager for DOS Main Menu


Starting ACE

The Array Configuration Editor is started by selecting the Configure → LogicalUnits/Drives... option from the DRM main menu.

The first time you start ACE, you will be presented with a series of <Array TypeIdentifier > panels and required to select a configuration layout for your arraysubsystem. Scroll through the layout options using the up/down arrow keys until youget to layout Generic 5 , Configuration 12 of 15 . Select this configuration and assigna name to the array controller. This is the name that will be used to identify thiscontroller and distinguish it from others that you may attach to later. The defaultidentification is the serial number of the array controller. You can assign any namehere, but it would be most useful to use one that will help you identify the controller,such as a location code or system name. You can change the ID of the controller atany later time using the Layout option from the ACE Drive window or from theDRM main menu (See “Identify the Controller or Change the Name” on page 222).You will then be presented with the ACE display. The next time you start ACE, youwill jump directly to this display.

Figure 101 shows the ACE display, which is made up of two parts: the Drivewindow (left side) and the Logical Unit window (right side). You can tell whichwindow is active because the label Drive Status or Logical Unit (LUN) Status ishighlighted and the options for that window appear in the bottom (right or left) halfof the screen.

You can switch between the Drive window and the Logical Unit window by pressing<Tab>.

Figure 101. The Array Configuration Editor (ACE) Display


The Logical Unit Window

Use the Logical Unit window to:

v View the status, device ID and device number of each logical unit

v Determine which drives make up the logical unit

v Identify (blink the activity lights) of the drives in the logical unit

Figure 102 shows the Logical Unit window. The upper half of the window, theLogical Unit Status display, shows information about the drive groups and logicalunits attached to the controller you are accessing.

A message indicating the amount of capacity remaining in the highlighted drivegroup appears below the Logical Unit Status display. Also shown in Figure 102 arethe options available from the Logical Unit window. The arrow indicates a secondpage of options that is access by pressing <O>. For normal maintenance, only theIdentify option will be used. The remaining options may be required for extendeddebugging and analysis under the direction of your next level of support.

Accessing Logical Units in ACE

When you use the the Array Configuration Editor (ACE), you access all the logicalunits assigned to a selected controller. You select the controller by physicallyconnecting to it over a serial line. The logical units you then access depend on thetype of controller you selected.

v On a single (non-redundant) controller, you access all logical units attached tothat controller by selecting the controller.

v On an active/passive pair of redundant controllers, you access all logical unitsattached to the pair by selecting the active controller.

v On an active/active pair of redundant controllers, you can access all logical unitsassigned to the active controller you selected.

Figure 102. The Logical Unit window


Note: You must keep in mind the difference between the logical units attached toa controller and the logical units currently assigned to a controller. Beingattached means that the drives containing the logical units are physicallyconnected to the controller. Being assigned to a controller means that thecontroller is currently servicing I/O to the logical units contained on thedrives.

Each controller in the pair is attached to all the logical units. Eachcontroller in the pair may have some logical units assigned to it. No logicalunits can be assigned to more than one controller. The controller servicesI/O to its assigned logical units. You can change assignment, but notattachment.

ACE will display all the drives attached to the active controller youselected, even though you cannot access those drives because theycontain logical units assigned to the other active controller in the pair. Youcan always access ″spare″ drives (those drives with a status of ″2″) fromeither active controller because these drives do not contain logical units.Any logical units created on these spare drives are automatically assignedto the controller you selected when you started ACE.

The Logical Unit Status Display

The Logical Unit Status display is located in the upper half of the Logical Unitwindow (see Figure 103). It shows the following information about logical units (anddrive groups) configured on the array controller you are accessing:

v drive group they belong to

Note: The drive group numbering can change when new LUNs are created ordeleted.

v Their LUN number

v Statuses (see “Logical Unit Statuses” on page 216).

v RAID level

v Device number and device ID

v Capacity in megabytes (MB)

Figure 103. The Logical Unit Status Display


For example, in Figure 103 on page 215, LUN 0 has been configured as RAID level5. It has an ″optimal″ status, device ID of ″CAM500032″ and 333 MB of capacity.LUN 0 is in drive group 1, which also includes LUN 1 and LUN 2. XXX MB of freecapacity remains in drive group 1. Also in Figure 103 on page 215, you can see thatLUN 3 is a RAID 5 logical unit with a status of ″degraded″. The Drive Matrix in thedrive window would indicate which drive is the source of the problem.

Logical Unit Statuses

The logical unit statuses that may appear in the ACE Logical Unit Status display areshown in table Table 46.

Note: The DRM Status menu item displays slightly different logical unit statuses.To view them, select Status → Logical Units from the DRM main menu. See“Checking Array Status” on page 226 for more information.

Table 46. ACE Logical Unit (LUN) Statuses

Status Description

Creating This logical unit is in the process of being created.

Dead

The logical unit is no longer functioning. Either:

v LUN parameters have changed, but the logical unit has not been reformatted

v Drives have failed in one of the following conditions:

– RAID 0 - a drive has failed

– RAID 1, 3, and 5 - two or more drives have failed in a LUN

v The wrong drive was replaced

v Some component connected to the logical unit failed or returned an unexpected value(bad SCSI ID, bad channel number, etc.).

Check the Drive Matrix LUN status to help detect the cause of the error.

Format pending The LUN is preparing to format.

Formatting The LUN is in the process of formatting

Degraded

The logical unit is operating in degraded mode. It is functioning, but data must bereconstructed using data and parity from the good drives. Either:

v A single drive has failed (RAID 1, 3 and 5).

v Multiple drives have failed (RAID 1, 3 and 5).

v Some component connected to the logical unit failed or returned an unexpected value(bad SCSI ID, bad channel number, etc.).

Check the Drive Matrix LUN status to help detect the cause of the error.

Optimal The array is operating at an optimal level.

Reconstructing The array controller is currently reconstructing data on the logical unit.

The Drive Window

The Drive window is used to view the statuses and locations of all the drivesassigned to a particular array controller.

Figure 104 on page 217 shows the Drive window. The upper half of the window, theDrive Matrix, displays the current drive statuses and gives a representation of thedrives attached to the current array controller.


Within each drive position is a number giving the current status of the drive. InFigure 104, one drive has a status of ″3″, (failed), two drives have a status of ″80″(Global Hot Spare), seventeen drives have a status of ″0″ (optimal) and theremaining drives are nonexistent (″1″).

While you are in the Drive window, a brief explanation of the status of the currentlyhighlighted drive appears below the Drive Matrix. You can display a complete list ofall drive statuses by selecting Status (Drives) from the list of options. For acomplete description of each drive status, see Table 47 on page 219.

Also shown in Figure 104 are the options available from the Drive window. Thearrow indicates a second page of options that is access by pressing <O>. Fornormal maintenance, only the Status and Update options will be used to explainand update the drive statuses that may appear in the Drive Matrix. The remainingoptions may be required for extended debugging and analysis under the direction ofyour next level of support.

Understanding the Drive Matrix

The Drive Matrix is located in the upper half of the Drive window. It displays thestatus and position of the drives attached to the array controller you specify whenyou start ACE.

Figure 104. The Drive window


When you first started the Array Configuration Editor (ACE), you should haveselected the Generic 5 (Configuration 12 of 15) layout (see “Starting ACE” onpage 213). If the Drive Matrix layout does not resemble Figure 105, then you willneed to change the layout configuration using the <L> option from the menu ofoptions in the bottom half of the Drive window.

The Drive Matrix is designed to be able to represent all supported configurations. Toprovide maximum performance, but still allow for expansion, the device drawers canbe configured as either two 5-drive SCSI buses or one 10-drive bus. There is abridge enable option bit on the back of the drive drawer that controls this feature.(See “Host and Drive ID Numbers” on page 42 for details). For device drawersconfigured with a singled 10-drive bus, the row in the Drive Matrix displayrepresenting the channel connected to that drawer will closely represent thephysical layout and drive numbering for the drawer. For device drawers configuredwith two 5-drive buses, though, there will actually be two rows in the Drive Matrixdisplay to represent each channel connected to that drawer, and the 5 drivesnumbered 08 - 12 in the Drive Matrix display will always show up with a status of″01″ (Nonexistent drive).

In large configurations, where 4 or more device drawers are installed andconnected to a single controller, some of the device drawers must be configuredwith a single, 10-drive bus and a single SCSI connection to the controller. In such aconfiguration, the drives will be numbered as shown in Figure 106.

In configurations with 3 or fewer device drawers, it is likely that all the drawers willbe configured with two 5-drive buses with 2 SCSI connections to the controller. In

Figure 105. The Drive Matrix

Figure 106. Device Drawer with Single Drive Bus (Bridge Disable OFF)


such a configuration, the drives will be numbered as shown in Figure 107 .

Drive Statuses

The status of a drive always appears as a number in the Drive Matrix. When youselect the individual drive, a brief explanation of the status of the selected driveappears below the Drive Matrix.

Notes:

1. You can see an expanded description of the status by highlighting the desireddrive, then pressing ″X″.

2. If you want to see a complete list of the drive statuses, from the Drive windowoptions, select Status → Drives .

3. The DRM Status menu item displays slightly different drive statuses. To viewthem, select Status → Drives from the DRM main menu. See “Checking ArrayStatus” on page 226 for more information.

The drive statuses that may appear in the ACE Drive Matrix display are shown inTable 47.

Table 47. ACE Drive Statuses

Status Description

00 - Optimal drive The drive is functioning normally.

01 - Nonexistent driveNo drive is connected to the array at this position. Either there is no drive physicallyconnected to the array. or you have deleted the drive.

02 - Spare driveThe drive is connected to the array, but not configured into a logical unit or assignedas a hot spare.

03 - Failed driveThe drive has experienced an error and has been failed by the array controller for anunknown reason, or it has been failed by a user. Replace the failed drive as soon aspossible.

04 - Replaced drive The drive has just been replaced, is being formatted, or is being reconstructed.

06 - No information availableThe array controller detected that the drive has either a different sector size, capacity,serial number, SCSI Channel, or ID than what the array controller expected. You needto replace the drive.

07 - This is the ControllerThis status is not a drive status - it indicates the Controller location of the arraycontroller in the array. This status only appears in specific configurations.

08 - Drive being formatted The drive is currently being formatted or is currently reconstructing.

Figure 107. Device Drawer with 2 Drive Buses (Bridge Disable ON)


Table 47. ACE Drive Statuses (continued)

Status Description

09 - Wrong drive replaced

You replaced the wrong drive. The drive that you removed from the array subsystemhad an ″Optimal″ status and there is still a failed drive in the array.

If you are not writing data to the logical unit, replacing the drive you removedimmediately should restore the logical unit and prevent data loss. In other instances,you may be able to restore the array without losing any data by ″reviving″ the drive.Call your next level of support for direction.

11 - Non-supported Channel The array controller cannot detect a drive at this location.

13 - Failed drive, readoperation

The drive has experienced read errors and has been failed by the array controllerbecause it could not reconstruct. Replace the failed drive as soon as possible.

14 - Drive format initiated The replaced drive is being formatted.

16 - Incompatible drive,sector size

The drive is formatted with the wrong block size. The drive must be formatted beforereconstruction.

17 - This is the AlternateController

This status is not a drive status - it indicates the Controller location of the alternatearray controller in the array. This status only appears in specific configurations.

18 - Drive format is pending The drive is in the process of being formatted.

21 - Non-supported SCSI ID The controller does not support drives with this SCSI ID.

23 - Failed Drive - time-outThe controller is unable to access this drive, but is aware that a drive was at thislocation.

24 - Drive beingreconstructed

The replaced drive is being reconstructed.

26 - Incompatible drive,capacity wrong

The drive has less than the minimum capacity required to support the LUN that isattempting to reconstruct.

31 - Non-supported channeland ID

The controller will not support drives at this location.

33 - Failed drive, formatoperation

The drive has experienced either format command or data reconstruction errors andhas been failed by the array controller. In any case, replace the failed drive as soon aspossible.

36 - Incompatible drive,mode parameters

The drive contains mode parameters from another RAID controller that areincompatible with parameters on the current system.

43 - Failed drive, writeoperation

The drive has experienced write errors and has been failed by the array controller,which will attempt to recover a RAID 1, 3 or 5 LUN drive. Replace the failed drive assoon as possible.

46 - Incompatible drive,serial number

The drive has the serial number of another RAID controller.

53 - Failed drive, by usercommand

The drive has been failed by the array controller at the users request. Replace thefailed drive as soon as possible.

56 - Incompatible drive,channel

The drive was set up to run on a different drive channel, probably when it waspreviously in use.

66 - Incompatible drive, IDThe drive was set up to run on a different drive ID, probably when it was previously inuse.

70 - Controller store isinvalid

The drive has experienced write errors when the array controller was unable to writethe configuration data from the subsystem to the array. Replace the failed drive assoon as possible.




Table 47. ACE Drive Statuses (continued)

Status Description

73 - Failed drive, controllerstore


76 - Incompatible drive,controller






80 - Global Hot Spare onstandby

This is a Global Hot Spare drive. It will immediately replace any failed drive in thearray that has the same or smaller capacity.

83 - Failed Global Hot Spare The Standby Global Hot Spare drive has failed.

90 - Global Hot Spare in use The Global Hot Spare drive is in use.

93 - Failed in use Global HotSpare

The active Global Hot Spare drive has failed.

??

ACE was not able to obtain a good status from the array. The array may not bepowered up, may not be connected properly, a driver may not be loaded, and so on.Press <U> to attempt to update the display. If the status remains, check yoursubsystem and its connecting cables.

Navigating in ACE

To move around and select elements in ACE, use the keys shown in Table 48. Themouse cannot be used to navigate in ACE.

Table 48. Navigating in ACE

Key Function in Drive Window Function in Logical Unit Window

TABMoves the cursor to the Logical Unitwindow.

Moves the cursor to the Drive Window.

Space BarMoves the cursor to the next availabledrive in the Drive Matrix.

Moves the cursor down in the Logical UnitStatus display.

Down ArrowMoves the cursor down in the DriveMatrix.

v Moves the cursor down in the LogicalUnit Status display.

v Moves the cursor to each logical unitthat can be changed.

Up Arrow Moves the cursor up in the Drive Matrix.Moves the cursor up in the Logical UnitStatus display.

Right Arrow Moves the cursor right in the Drive Matrix. N/A

Left Arrow Moves the cursor left in the Drive Matrix. N/A

ENTERMoves the cursor to the next availabledrive in the Drive Matrix.

Executes actions.

UUpdates or refreshes the ACE screen display. While ACE is updating, it displays theword WORKING. ACE automatically updates the screen every 30 seconds.

Q Quits the current function or exits ACE.


Identifying Drives and Logical Units

If you have multiple logical units on an array subsystem or have multiple activecontrollers, it is sometimes difficult to keep track of which devices are which. TheIdentify option in the Logical Unit window helps you identify the physical disk drivesand logical units represented in the Array Configuration Editor (ACE) display.

Use the following procedure to identify drives and logical units in ACE:

Note: This option may not work on a dead or degraded logical unit (depending onthe state of the unit). In this case, you will be able to determine the locationof the failed drives by the fault light. However, this may not identify whichlogical units are affected.

1. Start DRM (see “Starting DRM” on page 211).

2. Start the Array Configuration Editor (ACE) by selecting Configure →Logical Units/Drives from the DRM main menu (see “Starting ACE” onpage 213).

The ACE screen appears. You should now be in the Logical Unit window.

3. Using the up and down arrow keys, select a logical unit and press <I>.

The drive activity lights on the drives in the selected logical unit will startblinking, enabling you to determine where the drives in the selected LUNare physically located.

4. The lights will keep blinking until you exit the operation by pressing <Q>

Identify the Controller or Change the Name

When you first start the Array Configuration Editor (ACE) and define the drivelayout, you are asked to assign a name to the array controller. Identifying thecontroller is especially useful if you have several disk arrays installed and you wantto distinguish among them.

You can identify a controller or change the name at any time from the DRM mainmenu.

To identify the controller:


2. Select Status → Controllers .

To change the name of the controller:


2. Select Configure → Controller Name .

3. Select the appropriate controller (press the insert key and then use the up anddown arrows to highlight a controller from the list and then <ENTER> to select).

4. Enter the new name and press <ENTER>

Scan the Bus for Array Devices

Note: Most scans are automatic. For example, DRM scans for devices each timeyou start it. Similarly, whenever you leave the Array Configuration Editor(ACE), DRM automatically scans the array for any changes that may havebeen made to logical units while you were in ACE.


To scan the array manually from DRM:


2. Select Maintenance → Scan For Devices .

You can also re-scan the array controller you are currently connected to from withinACE by selecting <U - Update/Refresh> from the Drive window.

Using the Array Monitor

The Array Monitor in RAID Manager for DOS scans the logical units, drives, andcomponents (power supplies and fans) attached to an array controller and notifiesyou if it finds a failed component.

The operating system should have its own utility to monitor the array which will bebetter suited to determine the status of the array components. However, the ArrayMonitor in DRM is still a convenient tool to use to quickly determine the status ofarray components when using DRM to service the subsystem. It is also a good wayto determine whether DRM is communicating correctly with the array.

The Array Monitor displays the following:

v When you first start the Array Monitor, it displays any non-optimal status found onan array component.

v After the initial scan, it displays any status change (even from a non-optimalstatus to an optimal status) that occurs.

The Array Monitor screen shows the following information:

Item subsystem component affected by the statuschange.

Previous Status of the affected component, if available.

Current Status of the affected component.

Description of the status change.

Action recommended steps to take to correct the problem,if any.

Important: The action recommended by the ArrayMonitor usually assumes that RAIDManager for DOS is the only serviceinterface to the subsystem. Typically,this will not be the case, and the hostservice interface should be used toperform the necessary service actions.

You can take the following actions after viewing the message:

Save to save the message to the default array monitor log file. The file can holdonly one message, so saving the current message deletes any othermessage in the file. See the next section for a description of this log. Afterthe message is saved, the Array Monitor resumes polling.

Save Asto save the message to a file other than the default array monitor log file.You are prompted for the file name after selecting this option. If you enter


the name of an already existing file, any message in that file is overwritten.After saving the message, the Array Monitor resumes polling.

Continueto resume Array Monitor polling without saving the message. If you do notfix the condition indicated by the current message, the message will notappear again unless you leave the Array Monitor and restart it.

Quit to exit Array Monitor.

Important: You can create a batch file for the Array Monitor. If you create a batchfile, the monitor will perform the operations specified in the batch filewhenever an error occurs, instead of displaying a message on thescreen. See “Creating an Array Monitor Batch File” on page 225 formore information.

The Array Monitor Log

The Array Monitor log is the file the Array Monitor writes to if you select Save afterviewing the Array Monitor message. The log can hold one message only, and isoverwritten each time you select Save. If you want to keep a record of ArrayMonitor operations, you will have to use unique file names each time you start theArray Monitor or save messages using Save As in the message viewing screen.

Each message contains the same information that Array Monitor displays onscreen: item, previous status, current status, description, and action.

You can view the log files later:

v View the default log file by selecting Options → View Log → View Monitor Log .

v If you enter a different file name, you can view this file by selecting Options →View Log → View Other File .

What To Do When An Error Is Displayed by The Array Monitor

When the Array Monitor displays an error, do the following:

1. Read the error message, noting the type of status change and the componentaffected.

2. Save the message to a file using either the Save or Save As option.

3. Read the Action part of the message, but do not perform the recommendedaction yet . Service actions should be performed from the host service interface,not RAID Manager for DOS, unless directed by your next level of support.

4. Use the service interface from the host.

Starting the Array Monitor

Use the following procedure to run the Array Monitor from RAID Manager for DOS


2. Select Status → Monitor Arrays .

3. When prompted, specify the following:

v How often you want the Array Monitor to scan the array controllers.

v Whether you want a PC alarm to sound if a status change occurs.

v What default log file you want to use.


Note: When the Array Monitor first start, it displays any non-optimal status found.After this initial scan, it scans the array controllers for any change in status(even from non-optimal to optimal).

Creating an Array Monitor Batch File

Instead of displaying a message on the screen, Array Monitor can execute a batchfile. This batch file could, for example, save all the error messages into one largearray monitor log on your disk.

Use the following procedure to create a batch file for the Array Monitor.

1. Create the batch file and save on the DRM disk.

2. The first parameter in the batch file (%1) is always the default array monitor log.

3. Modify the drm.cfg file on the DRM disk. Put the full path and name of the filein the line after:

MONITOR_ALERT_SCRIPT =

4. Start the Array Monitor in DRM. If the monitor finds an error, it will perform theactions in the batch file instead of displaying the message on the screen.

Example:

Assume you want to store all the error messages from the array monitorin a single file. You also want to be notified on the screen when an erroroccurs. You could write the following batch file:

type %1 >> errmess.logecho offecho "Warning! Array Monitor has found an error!"

echo "Check the errmess.log file immediately!"

pause

The first line of the file concatenates the contents of the default monitorlog to a file called errmess.log. The subsequent lines display a messageon the screen and wait for you to acknowledge it. (The array monitor willnot continue running until you acknowledge the message. Press any keyand the Array Monitor continues scanning.)

If you named this batch file warning.bat, then you would need to addthis name, along with the path, in the drm.cfg file after the line:MONITOR_ALERT_SCRIPT =.

Diagnostics

Run diagnostic tests if the host is having trouble communicating with the array or ifyou are having trouble communicating with the array over the serial line. Thesetests operate only on active controllers. In addition, you can only test the data pathto an active controller with functional logical units.

From the DRM menu, select Diagnostics . The two diagnostic tests are:

Controller self-test resultsreturns the results of the last controller self-test performed during power-up.It dos not perform another test.


Test the data pathwrites and reads data from the array to insure that data is being written tothe array correctly.

Changing the Password

The first time you start DRM, you will be asked to enter a password of your choice.The default password is RAID. If you just enter RAID for the password, you will beprompted for a new password each time you start the program. Therefore, changethe password to something other than RAID after you first start the program.

You can change the password later by selecting Options → Password from theDRM main menu and entering the desired password.

If you forget your password, you will have to make another copy of your originalDRM diskette and use the new copy to start the program. The new copy will havethe original, default password and will prompt you for a new password when youfirst start the program. See “Preparation Tasks” on page 209.

Display and Set the Battery Age

At times, it may be necessary to view or set the controller battery age from RAIDManager for DOS. There are three options from the RAID Manager for DOS menu:

Reset the Battery TimerThis option can be used to reset the battery date to the current date. Toaccess this option, select Maintenance → Reset the Battery Timer fromthe DRM main menu.

Set Battery AgeThis option can be used to manually set the battery age (in units of 90days). To access this option, select Maintenance → Set Battery Age fromthe DRM main menu.

Display Battery AgeThis option can be used to view the battery age (in units of 90 days). Toaccess this option, select Maintenance → Display Battery Age from theDRM main menu.

Checking Array Status

The DRM Status menu item displays slightly different logical unit statuses and drivestatuses than those shown in the Array Configuration Editor (ACE).

To view the logical unit statuses from the DRM main menu:


2. Select Status → Logical Units .

The DRM logical unit statuses are shown in Table 49 on page 227. Also, whenviewing DRM logical unit statues, you can press <F1> to see a list of possiblestatuses and their definitions.


Table 49. DRM Logical Unit (LUN) Statuses

Status Description

Dead - Drive failures

The logical unit is no longer functioning. Either:

v LUN parameters have changed, but the logical unit has not been reformatted

v Drives have failed in one of the following conditions:

– RAID 0 - a drive has failed

– RAID 1, 3, and 5 - two or more drives have failed in a LUN

v The wrong drive was replaced

v Some component connected to the logical unit failed or returned an unexpected value(bad SCSI ID or bad channel number, for example).

Check the Drive Matrix LUN status from Array Configuration Editor to help detect the causeof the error.

Dead - Formatting The LUN is in the process of formatting.

Dead - Waiting toformat

The LUN is preparing to format.

Dead - Wrong drive A user has placed the wrong drive in this drive location.

Degraded

The logical unit is operating in degraded mode. It is functioning, but data must bereconstructed using data and parity from the good drives. Either:

v A single drive has failed (RAID 1, 3 and 5).

v Multiple drives have failed (RAID 1, 3 and 5).

v Some component connected to the logical unit failed or returned an unexpected value(bad SCSI ID or bad channel number, for example).

Check the Drive Matrix LUN status from Array Configuration Editor to help detect the causeof the error.

Optimal The array is operating at an optimal level.

Parity Scanning The data parity is being checked on this LUN.

Parity Inconsistency An error in the data parity was found on this LUN.

Parity Scan Aborted The data parity check for this LUN was halted before completion.

ReconstructionInitiated

The array controller is currently reconstructing data on the logical unit.

To view the drive statuses from the DRM main menu, select Status → Drives . TheDRM drive statuses are shown in Table 50. Also, when viewing DRM drive statues,you can press <F1> to see a list of possible statuses and their definitions.

Table 50. DRM Drive Statuses

Status Description

Optimal The drive is functioning normally.

FailedThe drive has failed and is no longer functioning. Replace the drive as soon aspossible.

Formatting The drive is currently being formatted.

Newly replaced The drive has just been replaced.

Reconstructed The data on the drive is currently being reconstructed.

Warning The drive has been put in a warning state as a result of a read or write error.


Chapter 17. Installing the Remote Support Feature

Remote Support Attachment of the WTI Data Switch and Modem

If your customer ordered the Remote Support Feature (feature code 2713), thenyou will need to perform the procedures in this section to install, set up and verifythe modem and WTI APS-16 Data Switch.

Note: Setup of the switch and modem requires that you have a Service Terminalavailable and a terminal emulator program (such as HyperTerminal,ProComm or Kermit).

Remote Support Feature Initial Installation

Refer to Figure 108 when performing this procedure.

Setup notes:

1. The switch and modem require external power sources, provided by thecustomer.

Figure 108. Attachment of the Modem and WTI Switch to a IBM 2102 F10 Fibre Channel Storage Server


2. The modem requires an analog phone line, provided by the customer.

3. The switch and modem must reside within 150 feet of the IBM 2102 Model F10Fibre Channel Storage Server .

Set Up the WTI APS-16 Data Switch1. Check and set the line voltage on the back of the WTI switch to the proper line

voltage for your account (115V or 230V).

2. Locate the Setup Switches on the underside of the WTI switch and set all theswitches ON.

3. Assemble the RJ-45 Null modem cables:

a. Plug one end of the 150’ RJ-45 cable (p/n 05H9744) into the LDRJ-9Fadapter (p/n 05H9745).

b. Plug the other end of the RJ-45 cable into the LDRJ-9FNL adapter (p/n08L7980).

Note: The LDRJ-9F and LDRJ-9FNL adapters look very similar. Make surethe correct connector is at each end of the RJ-45 cable.

c. Repeat with the remaining RJ-45 cable and adapters.

4. Connect the WTI switch to the Controller Module:

a. Connect the LDRJ-9F end of one of RJ-45 null modem cable assemblies toport #3 of the WTI switch.

b. Connect the other end (the end with the LDRJ-9FNL adapter) of the RJ-45null modem cable assembly to the top RS232 port on the back of thecontroller module.

c. Repeat with the other RJ-45 null modem cable assembly to connect port #4of the WTI switch to the bottom RS232 port on the back of the controllermodule.

5. If you have additional controllers to connect to the WTI switch, then repeatsteps 3 and 4 using the additional cables and adapters and connect theremaining ports of the WTI switch (ports #5-#16, do not use ports #1 or #2) tothe RS232 ports on the back of the controllers.

6. Connect the power cable to the WTI switch, plug the cable into an AC powersource and power on the WTI switch.

7. Initialize the WTI switch to the default settings:

a. Simultaneously press the SET and CLEAR buttons on the front of theswitch.

b. Release the CLEAR button, wait one second, and then release the SETbutton.

Note: This needs to be done only once after changing the Setup Switcheson the bottom of the switch.

Configure the WTI APS-16 Data Switch1. Connect the Service Terminal to the WTI switch:

a. Use the RAS cable (p/n 08L8045) that shipped with the IBM 2102 ModelF10 Fibre Channel Storage Server .

b. Connect one end of the RAS cable to the serial port of the service terminal.

c. Connect the other end of the RAS cable to port #1 of the WTI switch.

2. Start the terminal emulator on the service terminal.

a. Set up the terminal emulator for a direct connection through the appropriateserial port (typically COM1 or COM2).


b. Set the port settings for 8 data bits, no parity bits and 1 stop bit (8/N/1).

c. Set the baud rate for 9600 bits per second.

d. Set the Flow control to hardware (or RTS/CTS).

e. Set the emulation mode to Auto Detect. If there is not an auto detectselection, then select VT100.

f. If required, select the default code page.

g. If required, set the host type to ASCII.

3. Initiate the connection from the terminal emulator.

4. Issue the Wake Port command to the WTI switch:

a. Type ″/|E″ (forward slash, then the [Ctrl] and [E] keys simultaneously) andpress [Enter] .

b. If the password feature has been enabled, the switch will prompt the user toenter a password. Key in the password and then press [Enter] .

The APS> prompt will appear, indicating that the command mode is active.

If the APS> prompt is not displayed, this may indicate a communicationproblem. Check the following:

v Cable Connection: Check the cable connection between the WTI switch andthe PC. Make certain the cable connectors are firmly seated.

v Communication Parameters: Make certain the WTI switch and terminalemulator are using compatible parameters (baud rate, handshaking, data bits,etc.).

Note: From the APS> prompt, you can type ″/H″ [Enter] at any time to displaythe Help Screen (Figure 109 ).

5. Define the Site ID.

a. Type ″/F [Enter] ″. The Site ID Prompt will be displayed.

b. Key in the desired text and press [Enter] .

COMMAND MENU:

/¬E Wake-up port/X Sleep - only accepts Wake-up command/H Help - displays command list/S Status - displays status screen +--------------------+/W [n] Who - displays port parameters | n Port # or name |/C <n> [n] Connect - local [remote] | N Port # |/D <n | ... | *> Disconnect | | "or" |/E <n | ... | *> Erase Buffer | * "all" |/I Initialize / test unit | < > Required entry |/F Enter Site ID | [ ] Optional entry |/J Read Site ID +--------------------+/P [n] Set Port Parameters/U Read Port Parameters/L-<N> Load Port Parameters/G-00 Reinitialize All Ports

/D, /E, /I commands: add /Y to bypass "Are you sure (y/n)?"

Figure 109. Help Menu.

Chapter 17. Installing the Remote Support Feature 231

v The Site ID is a user defined string that can be used to identify this WTIswitch and distinguish it from others that will be accessed by supportpersonnel.

v The Site ID string can be up to 32 characters.

v The Site ID string cannot include unprintable ASCII characters, such asnulls or line feeds.

v The Site ID will be cleared when the WTI switch is initialized to defaultsettings.

c. To display the Site ID, type ″/J [Enter] ″.

6. Configure the Ports:

a. Type /S [Enter] to display the System Status Screen. This display showsthe current status and configuration of each port.

b. Configure the resident port (port #1):

1) Type ″/P 1 [Enter] ″ to configure port #1.

The port Configuration menu will appear as shown in Figure 110 .

2) Enter a ″1″ to select the PORT NAME Option.

3) Set the name for port #1 to ″resident ″.

4) If desired or requested by the customer, set a password by selectingoption ″2″ from the Port configuration Menu.

5) Set the Timeout Disconnect (option ″11″) to Off .

6) Exit the Configuration Menu for this port by typing |X ([Ctrl] + [X] ).

c. Configure the modem port (port #2):

1) Type ″/P 2 [Enter] ″ to configure port #2.

2) Set the PORT NAME to modem .

3) Set the MODE to Modem .

When the Modem Mode is selected, the unit will display additionalprompts that are used to select the Reset String , Initialization Stringand Hang-Up String .

PORT PARAMETERS #01

1. PORT NAME: (undefined)2. PASSWORD: (undefined)3. BAUD RATE: 96004. BITS/PARITY: 8-None5. STOP BITS: 16. HANDSHAKE: RTS/CTS7. MODE: Any-to-Any8. COMMANDS: All9. LOGOFF CHAR: +10. SEQUENCE DISC: On11. TIMEOUT DISC: 15 Min12. MESSAGE TYPE: Verbose13. ECHO: On

Enter: "<" previous port,">" next port,"##" change parameter<CTRL-X> exit ...

Figure 110. Port Configuration Menu


4) Clear the Reset String parameter (overwrite with the [SPACE] key). ThePort configuration Menu should show this as (undefined) .

5) Clear the Initialization String .

6) Set the Hang-Up string to ATH0.

7) Exit the Configuration Menu for this port by typing |X.

d. Configure the remaining ports (ports #3-#16):

1) Type ″/P n [Enter] ″ to configure port #n.

2) Set the PORT NAME to an appropriate value that can be used touniquely identify the specific controller that is attached to this port.

v The Port Name can be up to 8 characters in length.

v When defining the Port Name, do not use ASCII Control Codes, theslash character (/), quotation marks (″), the asterisk character (*), orblank spaces.

v The Port Name cannot begin with a number.

3) Set the COMMANDS to Basic .

4) Set the Timeout Disconnect to Off .

5) Exit the Configuration Menu for this port by typing |X.

6) Repeat for each WTI port that is connected to a controller.

e. Type ″/S [Enter] ″ to display the System Status Screen again. The displayshould reflect the configuration changes you just made. A sample display isshown in Figure 111.

Verify Switch Connections to the Control Units

Note: You can only verify connections to controllers that are powered on andavailable.

1. From the APS> prompt, type ″/C 3″ to connect through port #3 of the WTIswitch.

SYSTEM STATUS VERSION 1.1

PORT | NAME | STATUS | BAUD | COM | HS | MODE | TIMEOUT | BUF | CTS-----+----------+--------+--------+-----+------+-------+---------+-------+-----01+ | resident | Free | 9600 | 8N1 | RTS | Any | Off | 0 | H02+ | modem | *Free | 9600 | 8N1 | RTS | Modem | 15 Min | 0 | H03 | SS1-CUA | Free | 9600 | 8N1 | RTS | Any | Off | 0 | H04 | SS1-CUB | Free | 9600 | 8N1 | RTS | Any | Off | 0 | H05 | SS2-CUA | Free | 9600 | 8N1 | RTS | Any | Off | 0 | H06 | SS2-CUB | Free | 9600 | 8N1 | RTS | Any | Off | 0 | H07 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L08 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L

| | | | | | | | |09 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L10 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L11 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L12 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L13 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L14 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L15 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L16 | | Free | 9600 | 8N1 | RTS | Any | Off | 0 | L

Figure 111. Port Configuration Menu


2. Enter the <Break> sequence implemented by the terminal emulator programyou are using (″ALT-B ″ in ProComm or Kermit, ″|[Break] ″ in HyperTerminal).

You should see the messagePress within 5 seconds: <ESC> for SHELL, <BREAK> for baud rate

displayed on the screen.

Note: If you see garbage characters on the screen, then you need to set thebaud rate on the controller. To do this:

a. Enter the <Break> sequence at 1 second intervals, until you see themessage

set baud rate: press <space> within 5 seconds

b. Press the [Space] bar.

3. Type ″[Enter] +++ [Enter] ″ to disconnect from the port.

4. Repeat steps 1 on page 233 through 3 to verify each additional WTI switch portthat is connected to a controller.

Set Up the Modem1. Turn Modem power off.

2. Connect the Service Terminal to the WTI switch:

v Locate the 10’ 9-pin to 25-pin serial cable. This should either be includedwith the switch (p/n 05H9743) or the equivalent cable may have beenordered separately (p/n 05H3299).

v Connect the 25-pin connector to the DTE port on the back of the modem.

v Connect the 9-pin connector to the serial port of the service terminal.

3. Turn modem power on.


v Set up the terminal emulator for a direct connection through the appropriateserial port (typically COM1 or COM2).

v Set the port settings for 8 data bits, no parity bits and 1 stop bit (8/N/1).

v Set the baud rate for 9600 bits per second.

v Set the Flow control to hardware (or RTS/CTS).

v Set the emulation mode to Auto Detect. If there is not an auto detectselection, then select VT100.

v If required, select the default code page.

v If required, set the host type to ASCII.


6. Type ″AT″ from the terminal emulator and verify the modem responds with″OK″.

If the modem does not respond, then the current modem configuration may beincompatible with the terminal emulator configuration (for example, the modemmay be set up to connect at a specific baud rate that is different than that ofthe service terminal) and you will have to reset the modem to the factoryconfiguration as follows:

a. Turn the modem power off.

b. Remove the small panel (approximately 1.5 inches X 0.3 inches with″DeskPorte FAST″ on it) from the front of the modem. There will be aseries of switches behind this panel.

c. Set the switches as shown (U = Up, D = Down) from left to right.


D D D D D D D U D D D D

Note: Only one switch is up. The remainder are down.

d. Turn the modem power back on.

e. Initiate the connection from the terminal emulator.

7. Issue the following string to initialize the modem and set the profile:AT&F*E1%U1$B9600&D0*W0&Y0

Press [Enter] . The modem should respond with ″OK″.

8. Instruct the terminal emulator to disconnect (or Hang Up) the currentconnection.

9. Turn modem power ″Off″.

10. If you had to modify the modem dip switches in step 6 on page 234, then youwill need to change them back to their original settings:

D D D D D D D D D D D D

Note: All switches should be in the down (D) position.

11. Turn the modem back on and check the LCD display. The display should show9.6.

Connect the WTI Switch to the Modem1. Disconnect the 9-pin side of the serial cable from the PC and connect it to port

#2 of the WTI switch.

Adding Additional Remote Support Connections to the WTI DataSwitch

If your customer ordered the additional remote support attachment feature (featurecode 2714), then you will need to perform the following procedure to connectadditional controllers to an existing WTI Data Switch.

1. Assemble the RJ-45 Null modem cables:

a. Plug one end of the 150’ RJ-45 cable (p/n 05H9744) into the LDRJ-9Fadapter (p/n 05H9745).

b. Plug the other end of the RJ-45 cable into the LDRJ-9FNL adapter (p/n08L7980).

Note: The LDRJ-9F and LDRJ-9FNL adapters look very similar. Make surethe correct connector is at each end of the RJ-45 cable.

c. Repeat with the remaining RJ-45 cable and adapters.

2. Connect the Controller Module to the WTI switch:

a. Connect the LDRJ-9F end of one of RJ-45 null modem cable assemblies tothe next available port on the WTI switch. Do not use ports #1 or #2 – theseare reserved.

b. Connect the other end (the end with the LDRJ-9FNL adapter) of the RJ-45null modem cable assembly to the top RS232 port on the back of theadditional controller module you are connecting.

c. Repeat with the other RJ-45 null modem cable assembly to the nextavailable port on the WTI switch, to the bottom RS232 port on the back ofthe controller module.


3. If you have additional controllers to connect to the WTI switch, then repeatsteps 1 on page 235 and 2 on page 235 using the additional cables andadapters and connect the remaining ports of the WTI switch (do not use ports#1 or #2) to the RS232 ports on the back of the controllers.

4. Connect the Service Terminal to the WTI switch:

a. Use the RAS cable (p/n 08L8045) that shipped with the IBM 2102 ModelF10 Fibre Channel Storage Server .


c. Connect the other end of the RAS cable to port #1 of the WTI switch.




c. Set the baud rate for 9600 bits per second.

d. Set the Flow control to hardware (or RTS/CTS).


f. If required, select the default code page.

g. If required, set the host type to ASCII.


7. Issue the Wake Port command to the WTI switch:

a. Type ″/|E″ (forward slash, then the [Ctrl] and [E] keys simultaneously) andpress [Enter] .

b. If the password feature has been enabled, the switch will prompt the user toenter a password. Key in the password and then press [Enter] .

The APS> prompt will appear, indicating that the command mode is active.

If the APS> prompt is not displayed, this may indicate a communicationproblem. Check the following:

v Cable Connection: Check the cable connection between the WTI switch andthe PC. Make certain the cable connectors are firmly seated.

v Communication Parameters: Make certain the WTI switch and terminalemulator are using compatible parameters (baud rate, handshaking, data bits,etc.).

Note: From the APS> prompt, you can type ″/H″ [Enter] at any time to displaythe Help Screen (Figure 112 on page 237).


8. Configure the New Ports:

a. Type ″/P n [Enter] ″ to configure port #n.

The port Configuration menu will appear as shown in Figure 110 onpage 232.

b. Set the PORT NAME to an appropriate value that can be used to uniquelyidentify the specific controller that is attached to this port.

v The Port Name can be up to 8 characters in length.

v When defining the Port Name, do not use ASCII Control Codes, the slashcharacter (/), quotation marks (″), the asterisk character (*), or blankspaces.

v The Port Name cannot begin with a number.

c. Set the COMMANDS to Basic .

d. Set the Timeout Disconnect to Off .

e. Exit the Configuration Menu for this port by typing |X.

f. Repeat for each WTI port that is connected to a controller.

9. Type ″/S [Enter] ″ to display the System Status Screen again. The displayshould reflect the configuration changes you just made. A sample display isshown in Figure 111 on page 233.

10. Verify Switch Connections to the Control Units.

Note: You can only verify connections to controllers that are powered on andavailable.

a. From the APS> prompt, type ″/C n″ to connect through port #n of the WTIswitch.

b. Enter the <Break> sequence implemented by the terminal emulatorprogram you are using (″ALT-B ″ in ProComm or Kermit, ″|[Break] ″ inHyperTerminal).

You should see the messagePress within 5 seconds: <ESC> for SHELL, <BREAK> for baud rate


COMMAND MENU:

/¬E Wake-up port/X Sleep - only accepts Wake-up command/H Help - displays command list/S Status - displays status screen +--------------------+/W [n] Who - displays port parameters | n Port # or name |/C <n> [n] Connect - local [remote] | N Port # |/D <n | ... | *> Disconnect | | "or" |/E <n | ... | *> Erase Buffer | * "all" |/I Initialize / test unit | < > Required entry |/F Enter Site ID | [ ] Optional entry |/J Read Site ID +--------------------+/P [n] Set Port Parameters/U Read Port Parameters/L-<N> Load Port Parameters/G-00 Reinitialize All Ports

/D, /E, /I commands: add /Y to bypass "Are you sure (y/n)?"

Figure 112. Help Menu.


Note: If you see garbage characters on the screen, then you need to setthe baud rate on the controller. To do this:

1) Enter the <Break> sequence at 1 second intervals, until you seethe message


2) Press the [Space] bar.

c. Type ″[Enter] +++ [Enter] ″ to disconnect from the port.

d. Repeat steps 10.a on page 237 through 10.c to verify each additional WTIswitch port that is connected to a controller.


Chapter 18. Drive Microcode Download

Downloading Drive Microcode from Windows NT using DriveDload

What is DriveDload?

DriveDload is a tool for downloading firmware from a Windows NT host to the harddisk drives in an array. DriveDload should be installed on the host system as part ofthe Fibre Channel Storage Manager installation process. If it is not installed, you willneed to have the customer install it from the Fibre Channel Storage Managerinstallation CD or from a set of installation diskettes (See “Installing DriveDload”).

Attention: You must not download firmware to a drive concurrent with activity tothat drive.

Updating drive microcode can potentially result in loss of data. Data contained in alogical unit (LUN) that is part of a drive being downloaded to could be destroyed.

Please ensure that:

1. All data contained in LUNs that contain the drives to be updated is backed upprior to continuing.

2. All I/O to LUNs that contain the drives to be updated is stopped prior tocontinuing. Attention: Be sure to stop the I/O from all the hosts connected tothe array, not just the host that is performing the download.

3. All Fibre Channel Storage Manager applications are closed prior to continuing.Fibre Channel Storage Manager applications cannot be run at the same time asthe DriveDload utility.

When to Use DriveDload

You will need to use DriveDload to download new drive firmware:

v To a single drive when you replace a drive and the replacement drive firmware isnot compatible with the array controller firmware

v To all drives in the array when new drive firmware is distributed that contains acritical fix

Installing DriveDload

If DriveDload is not already installed on the host system, then you will need to havethe customer install the program before you can proceed. You will need the FibreChannel Storage Manager installation CD or the set of DriveDload installationdiskettes.

Use the following procedure to install DriveDload in a standard Windows NTconfiguration:

Important:

v The installer must have administrator privileges to install thesoftware. The installation requires a restart of the operating system.Therefore, make sure that other users are not using the systemwhen installing this software.


v In the following examples, a: is designated as the floppy disk drive,c: is designated as the boot drive and e: is designated as theCD-ROM drive. Be sure to select the correct drives for your system.

1. Insert the Installation CD into the CD-ROM drive or the first installation disketteinto the floppy disk drive.

2. From the Windows NT task bar, select

Start → Settings → Control Panel → Add/Remove Programs .

3. Select Install

4. Select the DriveDload setup executable (either e:\DriveDload\setup.exe ifinstalling from a CD-ROM, or a:\setup.exe if installing from diskettes).

5. Follow the Install Wizard instructions to complete the installation.

6. When installation is completed, remove the CD or diskette and restart thesystem.

Starting DriveDload

Use the following procedure to start DriveDload in Windows NT:

1. Have the customer stop all I/O activity to the array. Attention: Be sure the I/Ofrom all the hosts connected to the array have been stopped, not just the I/Ocoming from the host that is performing the download.

2. From the Window NT task bar, select Start → Program Files → IBM FibreChannel Storage Manager → Service Tools → DriveDLoad .

The DriveDload main panel should appear (See Figure 113 on page 241).

Using DriveDload

When you first start DriveDload, the main menu appears:


At this point, the user is required to specify the setup parameters, the drivedownload file and select the device that is to be updated.

Important:

v You must verify that the setup parameters specify the correct Drive Type, Vendor,and Product ID for the IBM 2102–F10 controller.

v You must be very careful when selecting the drives to update and the drivedownload file to send. If you send the wrong code file to a drive, you may renderthe drive unusable. View the readme file that came with the firmware or consultthe support web site to determine the correct firmware files for specific drives.

v At no time during the code update process should the host system or the diskdrive be powered down. Powering down while the ROM is being updated canrender the drive unusable. Powering down during a RAM update is typicallyrecoverable, but not advisable.

1. Click the Open Firmware File icon or select File → Open from the menu bar tospecify the file that contains the new drive firmware to be downloaded. View thereadme file that came with the firmware or consult the support web site todetermine the correct firmware files for specific drives.

2. Click the Setup Program Parameters icon or select Options → Setup from themenu bar, to specify the following parameters:

v Time Out Value = 0

v Delay after Write Buffer (ms) = 10000

v Drive Type = IBM

Figure 113. DriveDload Main Menu

Chapter 18. Drive Microcode Download 241

v Controller Identifier from Standard inquire page:

– Vendor = IBM

– Product ID = 2102–F10

Attention: If the download procedure fails, return to the setup screen and verifythat the setup parameters are set correctly for the IBM controller.

3. Click the Select Device icon or select Options → Select Device from the menubar to bring up the Existing Devices screen.

4. Select the Controller Devices radio button.

The system will be scanned and a list of eligible devices will be displayed.Double click or highlight and click OK to select the device which you wish todownload to.

Note: Depending on the setup parameters, the device selection screen may listall SCSI devices that can be seen from the host. This will include theRAID controller devices as well as any local SCSI hard drive(s). If thelocal hard drive is a SCSI drive, it will typically show up as the firstselection in the device selection screen. When selecting a device, alwaysensure that the device vendor is IBM and the Product is 2102–F10.

If the device that is selected is a RAID controller device, then you will see adrive list that shows all of the drives that are attached to the controller.Otherwise, you will see a screen with only a single device entry.

Important: If the drive list only contains a single drive, then you have notselected a RAID controller device and you must not attempt todownload microcode. Go back to the device selection screen(Existing Devices ), making sure that the Controller Devices radiobutton is still selected, and select a controller device.

5. Select the drive or drives that are to be updated by checking the box(es) on theleft. If all drives are to be updated with the same drive download file, then youmay check the All Drives box.

v You can download microcode to unassigned and spare drives through anyRAID controller device attached to the array.

v In order to download microcode to drives that are part of existing LUNs, youmust select a device from the device selection screen with a LUN value thatcorresponds to a LUN that the drive is assigned to.

6. Click the Firmware Download through DAC Icon or select Options → DACDownload from the menu bar.

Note:

v It will typically take between 1 and 2 minutes per drive for thedownload to complete. While the download is taking place, a messagebox will be displayed saying ″Downloading to Drive: xx. Please wait...″.When the download is complete, the message box will disappear andthe status window should display an indication that the Drive FirmwareDownload was successful.

v As part of the normal drive firmware download process, the drive willreturn check status to a host command in order to off-load sense datato indicate that its firmware has been changed. Thus, somecommands in the status window will indicate a failed status. However,the final status shown in the status window should indicate that theDrive Firmware Download passed.


If a download operation to a drive fails, then the entry for the drive in error willbe highlighted in red. Make note of the drive that failed and the data in thestatus window and call your next level of support.

7. The revision field (Rev) for drives is automatically updated after the downloadsare complete. You can manually refresh the display by clicking the RefreshDrive List icon or select Options → Refresh List to update.

Note: Drive failure indication (red highlight) will be lost once the screen isupdated, so make note of any failures before refreshing the list.

Drive List DefinitionsCHID indicates the controller Channel (1-6) and SCSI ID (0-12) of the

drive.

STATUS indicates the drive status as reported by the controller in the DriveStatus field of the Array Physical Page (0x2A) Mode Sense data.

Vendor shows the manufacturer of the drive.

Product shows the product ID of the drive.

Rev shows the revision level of the drive. Once firmware is downloadedto a drive, the Refresh Drive List Icon should be clicked to updatethe REV fields of all drives.

Meg Bytes shows the capacity of the drive in megabytes.

Drive Mode Page Download

DriveDload can also be used to download mode pages to IBM drives. Thisprocedure is very similar to the procedure for downloading drive microcode above.For more detailed explanation of the following steps, refer to the correspondingsteps in the drive microcode download procedure above.

1. From the DriveDload main menu (See “Starting DriveDload” on page 240), clickthe Open Firmware File icon or select File → Open from the menu bar tospecify the file that contains the new drive mode pages to be downloaded.

2. Click the Setup Program Parameters icon or select Options → Setup from themenu bar to specify the setup parameters.

3. Click the Select Device icon or select Options → Select Device from the menubar to bring up the Existing Devices screen.

4. Select the Controller Devices radio button.

5. Select the drive or drives that are to be updated by checking the box(es) on theleft.

6. Click the Page Download through DAC icon or select Options → DAC PageDownload from the menu bar.

If the procedure fails or errors occur, verify that the program parameters are correct.If the program parameters are correct and the procedure still fails, make note of thefailure indications and call your next level of support.


Downloading Drive Microcode from HP-UX or SUN Solaris UsingdrvDLoad

What is drvDLoad?

drvDLoad is a tool for downloading firmware from an HP-UX or SUN Solaris host tothe hard disk drives in an array. drvDLoad should be installed on the host systemas part of the Fibre Channel Storage Manager installation process. If it is notinstalled, you will need to have the customer install it from the Fibre ChannelStorage Manager installation CD (See “Installing drvDLoad”).

Attention: You should not download firmware to a drive concurrent with activity tothat drive. Updating drive microcode can potentially result in loss of data. Datacontained in a logical unit (LUN) that is part of a drive being downloaded to couldbe destroyed.

Please ensure that:

1. All data contained in LUNs that contain the drives to be updated is backed upprior to continuing.

2. All I/O to LUNs that contain the drives to be updated is stopped prior tocontinuing.

3. All Fibre Channel Storage Manager and StorWatch RAID Fibre ChannelSpecialist applications are closed prior to continuing. The RAID managementapplications cannot be run at the same time as the drvDLoad utility.

When to Use drvDLoad

You will need to use drvDLoad to download new drive firmware:

v To a single drive when you replace a drive and the replacement drive firmware isnot compatible with the array controller firmware

v To all drives in the array when new drive firmware is distributed that contains acritical fix

Installing drvDLoad

If drvDLoad is not already installed on the host system, then you will need to havethe customer install the program before you can proceed. You will need the FibreChannel Storage Manager installation CD. Use following procedure to installdrvDLoad in a standard HP-UX or SUN Solaris configuration:

Attention: The installer will need super-user privileges to install the software.

1. Install the installation CD-ROM in the CD-ROM drive and mount if necessary

2. Extract the files from the CD-ROM using the tar command as follows:tar -xvf /cdrom/drvdload/drvdload.tar

where /cdrom is the mount point of the CD-ROM file system.

3. Dismount the CD-ROM if necessary and remove the CD-ROM.


Starting drvDLoadImportant:

1. All activity must be stopped to drives that will be updated.

2. All Fibre Channel Storage Manager applications and StorWatch RAID FibreChannel Specialist must be closed prior to starting the drvDLoad utility.

3. You must copy the new drive firmware file(s) to the host system before startingthe drvDLoad utility.

Use the following procedure to start drvDLoad on HP-UX or SUN Solaris:

1. Have the customer stop all I/O activity to the array.

2. Change to the directory containing the drvDLoad utility (the default is/usr/sbin/fcsm/drvDLoad):cd /usr/sbin/fcsm/drvDLoad

3. Enter:./drvDLoad

The SELECT CONTROLLER PATH screen will appear.

Using drvDLoad

When you first start drvDLoad, the SELECT CONTROLLER PATH screen appears:

SELECT CONTROLLER PATH

The active controller paths are listed below.There may be multiple paths to the same controller listed.Select a controller path or select "QUIT" to exit drvDLoad:

1) c7t4d02) c7t5d03) QUIT

Selection:

1. At the SELECT CONTROLLER PATH screen, select the controller path youwant to use to perform the drive microcode download.

2. At the SELECT DRIVE TYPE screen, select the drive type to be updated.

3. At the MICROCODE FILE PATH screen, enter the path to the appropriate drivefirmware file.

4. At the SELECT MICROCODE FILE screen, select the appropriate drivefirmware file.

5. At the SELECT DRIVE GROUP screen, select the drive group that you wish todownload to or select the ″ALL DRIVES″ option to download to all the drives oftype.

6. If the DRIVE GROUP CONFIRMATION screen or DRIVE TYPECONFIRMATION screen is presented, then read the screen information,confirm that all the criteria are met and select ″CONTINUE″.

v If you selected ″ALL DRIVES″, then the download will begin. Go to step 8.

v If you selected an individual drive group, then the SELECT DRIVE screenwill be presented. Go to step 7.

7. At the SELECT DRIVE screen, select an individual drive to be updated orselect ″ALL drives in ″ to update all the drives of type in the selected group.


8. The download process will begin. When the download process has completed,the DRIVE DOWNLOAD COMPLETION screen will be presented and willindicate if the download completed successfully or not.

If an error occurred, then copy the error information and call your next level ofsupport. Otherwise, continue at the next step.

9. At the DRIVE DOWNLOAD COMPLETION screen, press [ENTER] to return tothe SELECT DRIVE screen and select another drive to update or select″RETURN″ to return to the SELECT DRIVE GROUP screen.

10. When all the required drives of the selected have been updated, select″RETURN″ from the SELECT DRIVE GROUP screen to return to the SELECTDRIVE TYPE screen. Select another drive type to update or select ″RETURN″to return to the SELECT CONTROLLER PATH screen.

11. When all the required drives have been updated, select ″QUIT″ from theSELECT CONTROLLER PATH screen to end the utility.

Downloading Drive Microcode From An AIX Host

The Fibre Channel Storage Manager support for AIX contains a built in diagnosticService Aid to download microcode to the disk drives in the 2102 Fibre ChannelRAID subsystem. Refer to the Fibre Channel Storage Manager, Installation andUser’s Guide for the AIX Operating System, SC26-7290 for details.


Chapter 19. Controller Debug Shell

At times, normal error indications and debug procedures will not be sufficient forisolating a problem on the IBM 2102 Model F10 Fibre Channel Storage Server. Inthese cases, the next level of support may ask you to gather data or performprocedures from within the controller debug shell.

The controller debug shell provides an interface into the operating system runningon the controller processor. It provides access to a set of very powerful debugcommands, but incorrect usage of these can result in the loss of data. You shouldnot access the controller debug shell unless explicitly directed by a serviceprocedure or by your next level of support.

The following sections explain how to connect a PC to the controller and gainaccess to the debug shell.

Note: Connecting to the controller and accessing the debug shell requires that youhave a Service Terminal available and a terminal emulator program (such asHyperTerminal, ProComm or Kermit) that is capable of sending the <Break>sequence.

Accessing the Controller Debug Shell1. Connect the Service Terminal to the Controller

a. Use the RAS cable (p/n 08L8045) that shipped with the IBM 2102 ModelF10 Fibre Channel Storage Server.


c. Connect the other end of the RAS cable to the RS232 port on the back ofthe controller.

If you don’t know which controller you need to access the debug shell from,select controller A (the top controller).




c. Set the baud rate for 9600 bits per second

d. Set the Flow control to hardware (or RTS/CTS)


f. If required, select the default code page

g. If required, set the host type to ASCII

3. Initiate the connection.

a. Enter the <Break> sequence implemented by the terminal emulator programyou are using (″ALT-B ″ in ProComm or Kermit, ″CTRL-Break ″ inHyperTerminal).

You should see the message:Press within 5 seconds: <ESC> for SHELL, <BREAK> for baud rate



Note: If you see garbage characters on the screen, then you need to setthe baud rate on the controller. To do this:

1) Enter the <Break> sequence at 1 second intervals, until you seethe message:


2) Press the [Space] bar.

You should see the message:baud rate set to 9600

3) Enter the <Break> sequence again. You should now see themessage:

Press within 5 seconds: <ESC> for SHELL, <BREAK> for baud rate


b. Press the [ESC] key within 5 seconds

Note: If you are too late pressing the [ESC] key, then you will need to enterthe <Break> sequence again.

You will be presented with a login prompt.

4. Enter the shell password (the default password is infiniti ) and press [Enter] .

You are now in the Controller debug shell.

5. To exit the shell at any time, type ″exit ″ from the shell prompt.

Controller Debug Shell Commands

The following section describes many of the commonly used shell commands.

Note: Remember, you should only access the controller debug shell whenexplicitly directed by a service procedure or by your next level ofsupport .

Because these commands and the addresses listed are dependent on the controllerfirmware, they are subject to change without notice. If a command does not work oran address does not yield the expected data, consult your next level of support forupdated syntax and/or parameters.

Summary of Common Debug Shell CommandsTable 51. Controller Debug Shell Commands

Command Usage

Shell Commands to display LUN/Drive Status

cfgPhy ch,id displays contents of internal phydev structure

cfgPh ch, id displays piece header structure from DACstore

cfgDd ch, id displays contents of DACstore directory

cfgPbDev ch, id, lun displays LUN definition stored in DACstore on ch,id drive

cfgUnit lun displays detailed LUN information from memory

cfgUnitList displays LUN state for all LUNs

vdAll cmd performs cmd for all existing LUNs (e.g. vdAll vdShow)

vdShow displays detailed information about LUN configuration


Table 51. Controller Debug Shell Commands (continued)

Command Usage

ghsList displays information about Global Hot Spare drives

Shell commands to display RDAC status

arrayPrintSummary prints summary of array controller states, LUN ownership

arrayPrint prints detailed controller state information

rdsPrint prints contents of RDAC store

iconMgrSendPingPong sends test message to alternate controller and waits for reply

Shell Commands to modify LUN/Drive Status

isp cfgFailDrive devnum fails drive specified by devnum

isp cfgReplaceDrive devnum replaces drive specified by devnum

isp cfgSetDevOper devnum set drive status for drive specified by devnum to optimal (no reconstruct)

isp cfgDelVdisk lun deletes LUN

Shell Commands to modify RDAC status

isp rdacMgrSetModeActivePassive sets controller mode to active and alternate controller mode to passive

isp rdacMgrSetModeDualActive sets controller mode to dual active

isp rdacMgrTakeLunOwnership 0,lunlist takes over LUN ownership of luns specified in lunlist

isp rdacMgrAltCtlFail fails alternate controller (holds in reset) and takes ownership of LUNs

isp rdacMgrAltCtlResetRelease releases failed controller from being held in reset

Performance Monitor Shell Commands

mon monitors controller performance

syncShow displays level of cache usage

__PerfMonRestart resets performance counts

__PerMonReportPrt prints performance counts

Other Useful Shell Commands

showEnclosure Displays information about enclosure devices

ld < /Debug loads debug symbols

moduleListlists software modules and displays versions of bootware and applicationcode

dstDevs displays information about known drives

iosFdShow displays information about open Fds

printBatteryAge prints current, installation, expiration and warning time

rpaGetBatteryAgeprints the life of the battery in number of 90-day increments in decimal, hexand ASCII. This is the format (in hex) that the NVSRAM UserCfgRegion usesto set the life of the battery (e.g 2 yrs. = 0x8).

ccmStateAnalyze displays cache configuration manager debug information

vdAnalyze level displays virtual disk debug information

bufAnalyze level displays information about buf structures

cacheAnalyze level displays information about cache structures

srcDebugActiveIos lists active host commands (use to debug IOs)

srcC800Debug lists commands active on host SCSI chip (use to debug IOs)

i lists summary task information

Chapter 19. Controller Debug Shell 249

Table 51. Controller Debug Shell Commands (continued)

Command Usage

Ilists detailed task information, memory usage (8-9 pages, used for a hung orslowed down system)

tt tid dump task stack trace for task with address tid

d addr, len, widthdumps memory at address addr for len entries of width bytes (1, 2, 4). addrmay be a hex address or a variable name.

m addr, width modifies memory at address addr in entries of width bytes (2, 4)

memShow displays current and cumulative processor memory usage

vdMap lun, blockdisplays mapping for LUN block (devnum and block number), will give blocknumber to use for dump (dump 0x400000, #, 1)

VKI_CMN_ERR_MASK 0x0F sets debug error mask

VKI_CMN_ERR_MASK 0x00 resets debug error mask

sysReboot reboots controller (like power on reset)

reboot (or CTRL-X or CTRL-x ) reboots controller (like host bus reset)

sysWipe ***This will wipe out all data. It clears all configuration and sets default values.


Part 6. Appendixes


Appendix A. AIX Code Information

2102-F10 Error Log Sense Information

Below is a sample error log entry with some of the more important fields explained.---------------------------------------------------------------------------LABEL:IDENTIFIER: BC669AA7

Date/Time: Thu Oct 1 14:20:23Sequence Number: 83708Machine Id: 005461C34C00Node Id: mgmClass: HType: PERMResource Name: dac1Resource Class: arrayResource Type: ibm-dacLocation: 04-01-01VPD:

Manufacturer................SYMBIOSMachine Type and Model......INF-01-00ROS Level and ID............9300Serial Number...............1T81916892Device Specific.(Z2)........93000107Device Specific.(Z3)........93000107

DescriptionCONTROLLER HEALTH CHECK FAILURE

Probable CausesARRAY CONTROLLERCABLES AND CONNECTIONSARRAY DASD MEDIA

Failure CausesDASD MEDIAARRAY CONTROLLERCABLES AND CONNECTIONS

Recommended ActionsPERFORM PROBLEM DETERMINATION PROCEDURES

Detail DataSENSE DATA

0600 1D04 0000 00C0 0000 0004 0000 0000 0000 0000 0000 0000 0102 0000 7000 06000000 0098 0000 0000 8B02 0000 0000 0000 0100 0000 0000 0000 0000 0000 0000 00000008 1600 001D 0400 0000 C000 0000 0405 0000 3154 3831 3931 3638 3932 2020 20202020 9300 0100 0004 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000 001B F875 3130 3031 3938 2F31 3135 3932 3800 0000 0000 0000 0000 00000000 0000 50E8 D000 FF98 1001 0000 0000 0000 0000 0000 0000 0000 0000 0000 00000000 0000

To interpret this error log, you would follow the templatebelow. The SV, SS, AS, DS, and ASCQ fields are often the most useful to decode.

SENSE DATA Template:

CL00 SCSC SCSC SCSC SCSC SCSC SCSC SCSC SCSC RRRR RRRR RRRR SVSS ASDS EC00 SKIBIBIB IBSL X0X0 X0X0 ASCQ FRX1 X1X1 R1R2 TETR ASC1 ASC2 AFAF AFAF AFAF AFAF ESESESEP EPEP EPOC OCOC OCOC OCOC OCOC OCHI H1H2 SNSN SNSN SNSN SNSN SNSN SNSN SNSNSNSN SRSR SRSR 00LN LS00 00X2 X2X2 X2X3 X3X3 X3X3 X3X3 X3X3 X3X3 X3X3 X3X3 X3X4X4RL X5X5 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6 X6X6X6X6 X6X6 X7X7 X7X7 TSTS TSTS TSTS TSTS TSTS TSTS TSTS TSTS 0000 0000 RRRR RRRRRRRR RRRR YPYP YPYP YYVL VLVL RRRR RRRR Z0Z1 Z2Z3 Z4Z5 Z6Z7 S0F0 S1F1 RRRR RRCM


LOLO LOLO

---------------------------------------------------------------------------

ITEM DESCRIPTION

CL SCSI Command Length.

SC SCSI Command Issued.

SV

Status Validity:

1 Valid SCSI status.

2 Valid Adapter status.

3 Valid Driver status.

4 Valid Driver status.

SS

SCSI Status:

00 Good status (successful completion).

02 Check condition.

08 Busy status.

18 Reservation conflict.

22 Command terminated by device.

28 Queue full.

30 ACAactive.

AS

Adapter Status:

01 Host I/OBus error.

02 Transport Fault.

03 CommandTimeout.

04 No Device Response.

05 Adapter Hardware Failure.

06 Adapter Software Failure.

07 World-Wide Name Change.

08 Fuse or Terminal Power.

09 Transport Reset.

0a Transport Busy.

0b Transport Dead.

DS

Driver Status:

AA Failed to start command in fcparray_start.

EE LUNownership switch.

NOTE: Errors from EC through the reserved area before VP are scsi sense data from the 2102, and are valid ifstatus validity shows SCSI status. They may be valid in other cases, since the buffer is zeroed out before sense datais copied to it.


ITEM DESCRIPTION

EC

Error Code:

70 Immediate error (on current command as shown).

71 Deferred error (an error indication for a command already completed withgood completion, most likely a write into fast write cache).

SK

Sense Key:

00 No sense.

01 Recovered Error.

02 Not Ready.

03 Medium Error.

04 Hardware Error.

05 Illegal Request.

06 Unit Attention.

07 Data Protect.

0B Aborted Command.

0E Miscompare.

IB Information Bytes - usually the block address of the error or illegal request

SLAdditional Sense Length - the number of bytes following this one which are valid. Inmost cases this will be 0x98; in some cases, it may be 0x0A.

X0Command Specific Information. This is valid only for sense data after an unsuccessfulReassign Blocks command.

ASCQ Additional Sense Code and Qualifier. A full list of these is here.

FRField Replacable Unit. This along with the Additional FRU Information points to thefailed device on a hardware failure. See this table for more information.

X1Sense Key Specific Bytes. These are valid for Illegal Request errors. See 2102documentation for more information.

R1

Recovery Actions taken by the controller (Bit(s) and Meaning):

0–3 Reserved.

4 Drive command retried.

5 Failed drive.

6 Downed LUN.

7 Information logged.

Appendix A. AIX Code Information 255

ITEM DESCRIPTION

R2

Recovery Actions taken by the controller:

0 Check data used.

1–2 Reserved.

3 Issued Reassign Block command.

4 Issued Start Stop Unit command.

5 Reserved.

6 Asserted Reset signal on drive channel.

7 Reserved.

TE Total Number of Errors during this command.

TR Total Retry Count for this command.

ASC1 Most recent previous ASCQ associated with this command.

ASC2 Second most resent previous ASCQ associated with this command.

AF Additional FRU information. See FRU decode table for more information.

ES Error Specific Information.

EP Error Detection Point.

OC Original command CDB. In most cases will be the same as in SC.

HI SCSIID of the host which initiated this command.

H1 Host Descriptor High (see 2102 documentation).

H2 Host Descriptor Low (see 2102 documentation).

SN Serial Number (in ASCII) of this controller.

SR Software Revision Level of the controller microcode.

LN LUN number of the target LUN.

LS

LUN status of the target LUN:

00 Optimal.

20, 50, 60 Optimal with various background tasks in progress.

01 Degraded, waiting for repair.

41, 61, 02 Degraded, various repairs in progress.

04, 44, 54, 64, 74 Dead LUN.

X2 Drive Software Revision Level.

X3 Drive Product ID.

X4 Array Power-Up Status.

RL RAID level of the target LUN.

X5 Drive Sense Identifier. First byte is the channel/id of the drive.

X6 Drive Sense Data.

X7 Sequence Number. Controller’s internal sequence number for this I/O.

TSDate and Time Stamp. This is an ASCII date and time in the formatMMDDYY/HHMMSS.

VPPointer to array information (for all but switches) and pointer to router information (forswitches).


ITEM DESCRIPTION

YY Detail data validity (currently 0xFF).

VLVersion level of the software. This will be YYMMDD for internal releases and the form0432PP for an AIX 4.3.2 patch of level PP.

Z0-Z7

For failure to start (driver status valid and set to AA); counters for fail reasons:

Z0 Too many commands outstanding, array being recovered, waiting on timer toclear, or waiting for queue to clear.

Z1 A reset has failed, and the device is being closed.

Z2 A reset has failed, and we are retrying the reset.

Z3 There are no valid paths to either controller, or we are quiescing I/O for somereason (AENpoll, etcetera).

Z4 Waiting for outstanding commands before issuing an ioctl.

Z5 An ioctl is pending, and we are clearing commands before issuing it.

Z6 We are quiescing I/O before a switch.

Z0-Z7

For a switch (driver status valid and set to EE); switch characteristics:

Z0–Z2 Target mode for a switch (see CM).

Z3 Target mode for a switch (see CM).

Z4–Z7 Target LUN ownership bitmap for a switch.

S0, S1 Lowest byte of SCSI id of controller 0 or 1

F0, F1

Failure state of controller 0 or 1:

00–Z2 working

01 miscellaneous failure

02–Z7 communication failure

08–Z7 switch operation failed on an otherwise working controller

10–Z7 Command failure (timeout, or bad sense data).

40–Z7 Adapter failure not communication-related.

80–Z7 Hard failure (ICON, WorldWide Name Change, Hardware failure).

CM

Current operating mode:

00–Z2 Dual Active

10 Passive-Active

01 Active-Passive

40–Z7 Reset-Active

04 Active-Reset

LO Current LUNownership bitmap


Field Replaceable Unit (FRU) Codes

FRU Code Description

0x01

Host Channel Group

A FRU group consisting of the host SCSI bus, its SCSI interface chips and all initiatorsand targets on the bus.

0x02

Controller Drive Group

A FRU group consisting of the SCSI interface chips on the controller which connect tothe drive buses.

0x03Controller Buffer Group

A FRU group consisting of the controller logic to implement the on-board data buffer.

0x04

Controller Array ASICs Group

A FRU group consisting of the ASICs on the controller associated with the arrayfunctions.

0x05

Controller Other Group

A FRU group consisting of all the controller related hardware not associated withanother group. This includes the controller power supply.

0x06

Subsystem Group

A FRU group consisting of subsystem components that are monitored by the arraycontroller, such as power supplies and fans.

0x07Subsystem Configuration Group

A FRU group consisting of subsystem components that are configured by the user.

0x08

Sub-enclosure Group

A FRU group consisting of attached enclosure devices, including power supplies andother subsystem components in the sub-enclosure. Refer to “Additional FRUInformation” below for more information on the faulty component.

0x10 - 0xff

Drive Group

A FRU group consisting of a complete disk drive assembly. The first digit indicates theSCSI bus, the last digit the SCSI ID.

Additional FRU Information

Bytes 26 and 27 provide FRU Group Qualifiers for byte 14 (the primary FRU code).Byte 28 is an additional FRU group code, and Bytes 29 and 30 provide FRU GroupQualifiers for byte 28. Byte 31 is another additional FRU group code, with bytes 32and 33 providing FRU Group Qualifiers for it.

FRU Group Qualifiers for the Subsystem Group (0x06) are covered in the 2102hardware specification.

FRU Group Qualifiers for the Drive Group are simply reiterations of the channel/idvalue.

FRU Group Qualifiers for the Sub-Enclosure Group are as follows:


Most significant byte (bytes 26, 29, and 32):

Bit Meaning

7 Tray Identifier Enable (TIE)

6-4 Reserved

3-0

Sub-Enclosure Identifier

If TIE=1, this provides the tray identifier for the sub-enclosure beingdescribed. If TIE=0, the sub-enclosure identifier is defined as shownin the following table.

Channel Enclosure #1 Enclosure #2

1 0x01 0x06

2 0x02 0x07

3 0x03 0x08

4 0x04 0x09

5 0x05 0x0a

Least significant byte (bytes 27, 30, and 33):

Bit Meaning

7-5

Device State:

0 Optimal

1 Warning

2 Failed

3–7 Reserved

3-0

Device Type Identifier:

0x00 Unspecified

0x01 Device

0x02 Power Supply

0x03–7 Cooling Element

0x04 Temperature Sensors

0x06 Audible Alarm

0x07 Environmental Services Electronics

0x08 Controller Electronics

0x09 Nonvolatile Cache

0x0B Uninterruptible Power Supply

0x0C–0x13 Reserved

0x14 SCSI Target Port

0x15 SCSI Initiator Port


Disk Array Errors

Always run diagnostics when an error condition occurs to determine the correctaction to perform. Decoding error log sense information can sometimes help inunderstanding a problem.

Error and Meaning Description

FCP_ARRAY_ERR1

ARRAY OPERATIONERROR

A permanent hardware error involving the disk array media hasoccurred.

FCP_ARRAY_ERR2


A permanent hardware error has occurred.

FCP_ARRAY_ERR3


A permanent error was detected by the array adapter.

FCP_ARRAY_ERR4


A temporary error has occurred within the array, communications,adapter, etcetera.

FCP_ARRAY_ERR5

UNDETERMINEDERROR

The cause of this error is unknown.

FCP_ARRAY_ERR6

SUBSYSTEMCOMPONENTFAILURE

A degradation condition has occurred other than a disk drive.

FCP_ARRAY_ERR7

CONTROLLERHEALTH CHECKFAILURE

A health check on the passive controller has failed.

FCP_ARRAY_ERR8

ARRAYCONTROLLERSWITCH

An abnormal condition caused an array controller switch to occur.

FCP_ARRAY_ERR9

ARRAYCONTROLLERSWITCH FAILURE

An array controller switch has failed.

FCP_ARRAY_ERR10

ARRAYCONFIGURATIONCHANGED

A logical unit has been moved from one controller to the other (mostlikely via the action of an alternate host).

FCP_ARRAY_ERR11

IMPROPER DRIVETYPE FOR DUALACTIVE MODE

This error should not be possible on the 2102 array, and exists forhistoric reasons only. FCP_ARRAY_ERR11 may be reused for a differenterror in the future.


Error and Meaning Description

FCP_ARRAY_ERR12

POLLED AENFAILURE

An automatic error notification has failed.

FCP_ARRAY_ERR13

ARRAYINTER-CONTROLLERCOMMUNICATIONFAILURE

self-explanatory.

FCP_ARRAY_ERR14

ARRAY DRIVEFAILURE

self-explanatory.

FCP_ARRAY_ERR15

CACHE BATTERYLOW/DATA LOSSPOSSIBLE

If a controller card was recently replaced, the cache batteries maynot have been fully charged. It can take two days for the cachebatteries to be fully recharged. During this time, errors will be loggedin the error log. Do not replace the controller.

FCP_ARRAY_ERR16

CACHE BATTERYCHARGE BELOW87.5%

If a controller card was recently replaced, the cache batteries maynot have been fully charged. It can take two days for the cachebatteries to be fully recharged. During this time, errors will be loggedin the error log. Do not replace the controller.

FCP_ARRAY_ERR17

WORLD-WIDE NAMECHANGED

A controller has changed world wide names (most likely either it wasreplaced without placing it in reset first, or cabling was changed sothat a different controller with the same SCSI ID is on the loop).

2102 Array Additional Sense Codes And Qualifiers (ASC/ASQ)

Many of the ASC/ASCQ code are identical to the ones used in normal disk drives.

This section lists the Additional Sense Codes (ASC), and Additional Sense CodeQualifier (ASCQ) values returned by the array controller in the sense data. SCSI-2defined codes are used when possible. Array specific error codes are used whennecessary, and are assigned SCSI-2 vendor unique codes 80-FFH. More detailedsense key information may be obtained from the array controller commanddescriptions or the SCSI-2 standard.

Codes defined by SCSI-2 and the array vendor specific codes are shown below.The most probable sense keys (listed below for reference) returned for each errorare also listed in the table. A sense key encapsulated by parentheses in the table isan indication that the sense key is determined by the value in byte 0x0A of theUser- configured region of the NVSRAM.

ASC/ASQ Sense Key Description

0000 0 No Additional Sense Information

0401 2

Logical Unit Is In Process Of Becoming Ready

The controller is executing its initialization functions on the addressed logical unit. Thisincludes drive spin-up and validation of the drive/logical unit configuration information.

0402 2 Logical Unit Not Ready, Initializing Command Required Start Unit command required

0404 2 Logical Unit Not Ready, Format In Progress



0481 2 Storage Module Firmware Incompatible - Manual Code Synchronization Required

0C00 4 Unrecoverable Write Error

0C01 1 Write Error Recovered With Auto Reallocation

0C80 4 Unrecoverable Write Error Due to Non-Volatile Cache Failure

0C81 4 Deferred unrecoverable error due to Memory Failure

1100 3

Unrecoverable Read Error

An unrecoverable read operation to a drive occurred and the controller has noredundancy to recover the error (RAID 0 or degraded RAID 1 or 5).

118A 6 Mis-corrected Data Error - Due to Failed Drive Read

1802 1 Recovered Data - Data Auto-Reallocated

1A00 5 Parameter List Length Error

2000 5 Invalid Command Operation Code

2100 5 Logical Block Address Out Of Range

2400 5 Invalid Field In CDB

2500 5 Logical Unit Not Supported

2600 5

Invalid Field In Parameter List

The controller received a command with a parameter list that contained an error.Typical efforts that return this code are unsupported mode pages, attempts to changean unchangeable mode parameter, or attempts to set a changeable mode parameter toan unsupported value.

2800 6

Not Ready To Ready Transition (Medium May Have Changed

The controller has completed its initialization operations on the logical unit and it is nowready for access.

2900 6 Power On, Reset, Or Bus Device Reset Occurred

2904 6Device Internal Reset

The controller has reset itself due to an internal error condition

2981 6

Default Configuration has been Created

The controller has completed the process of creating a default logical unit. There is nowan accessible logical unit that did not exist previously. The host should execute itsdevice scan to find the new logical unit.

2982 6 Controller Firmware Changed Through Auto Code Synchronization

2A01 6

Mode Parameters Changed

The controller received a request from another initiator to change the mode parametersfor the addressed logical unit. This error is to notify the current initiator that the changeoccurred.

2A02 6 Log Parameters Changed

2F00 6

Commands Cleared by Another Initiator

The controller received a Clear Queue message from another initiator. This error is tonotify the current initiator that the controller cleared the current initiators commands if ithad any outstanding.

3101 1,4Format Command Failed

A Format Unit command issued to a drive returned an unrecoverable error.



3200 4 Out of Alternates

3F01 6Drive Microcode Has Been Changed

Returned when new drive microcode has been downloaded.

3F8N 6

Drive Failed Because Of A Failed Write Operation

This is the result of an error that prohibits use of the drive. The value of N in the ASCQindicates the reason why the drive cannot be used.

0 The controller set the drive state to ″Failed - Write Failure″

1,3,4,8,A,F Not used

2 The controller set the drive state to ″Failed″ because it was unable tomake the drive usable after replacement.

5 The controller set the drive state to ″Failed - No response″

6 The controller set the drive state to ″Failed - Format failure″

7 The controller set the drive state to ″User failed via Mode Select″

9 The controller set the drive state to ″Wrong drive removed/replaced″

B The controller set the drive state to ″Drive capacity < minimum″

C The controller set the drive state to ″Drive has wrong block size″

D The controller set the drive state to ″Failed - Controller storagefailure″

E Drive failed due to reconstruction failure at Start of Day (SOD)


3F98 6 Drive Marked Off-line Due to Internal Recovery Procedure

3FBD 6The controller has detected a drive with Mode Select parameters that are notrecommended or which could not be changed. Currently this indicates that the QErr bitis set incorrectly on the drive specified in the FRU field of the Request Sense data.

3FC3 6The controller has detected a failed drive side channel specified in the FRU Qualifierfield.

3FC7 6

Non-media Component Failure

The controller has detected the failure of a subsystem component other than a disk orcontroller. The FRU codes indicate the faulty component.

FRU code and qualifiers identify the failed component.

3FC8 6 AC Power Is Lost, DC Power Is Being Supplied By A Hold-Over Battery

3FC9 6AC Power Is Lost, DC Power Supplied For A Maximum Of Two Minutes

The host should start its shutdown procedure.

3FCA 6 Standby Power Depletion Imminent

3FCB 6 AC Power Has Been Restored

3FD0 6 Write Back Cache Battery Has Been Discharged

3FD1 6 Write Back Cache Battery Charge Has Completed

3FD8 6 Cache Battery Life Expiration

3FD9 6 Cache Battery Life Expiration Warning



3FE0 6

Logical Unit Failure

The controller has placed the logical unit in a ″dead″ state. User data and/or parity canno longer be maintained to ensure availability. The most likely cause is a single drivefailure in a non-redundant configuration or a second drive failure in a redundantconfiguration. The data on the logical unit is no longer accessible.

3FEB 6 LUN marked DEAD due to Media Error Failure during SOD

40NN 4,6

Diagnostic Failure on Component NN (0x80-0xFF)

The controller has detected the failure of an internal controller component. This failuremay have been detected during operation as well as during an on-board diagnosticroutine. The values of NN supported in this release of the software are listed below.

80 Processor RAM

81 RAID Buffer (read/write cache)

82 NVSRAM

83 RAID Parity Assist (RPA) chip or cache holdup battery

84 Battery Backed NVSRAM or Clock Failure

91 Diagnostic Self Test failed non-data transfer components test

92 Diagnostic Self Test failed data transfer components test

93 Diagnostic Self Test failed drive Read/Write Buffer data turnaround test

94 Diagnostic Self Test failed drive Inquiry access test

95 Diagnostic Self Test failed drive Read/Write data turnaround test

96 Diagnostic Self Test failed drive Self Test


4300 4

Message Error

The controller attempted to send a message to the host, but the host responded with aReject message.

4400 4,B

Internal Target Failure

The controller has detected a hardware or software condition that does not allow therequested command to be completed. If the sense key is 0x04 indicating a hardwarefailure, the controller has detected what it believes is a fatal hardware or softwarefailure and it is unlikely that a retry would be successful. If the sense key is 0x0Bindicating an aborted command, the controller has detected what it believes is atemporary software failure that is likely to be recovered if retried.

4500 1,4Selection Time-out on a Destination Bus

A drive did not respond to selection within a selection time-out period.

4700 1,B

SCSI Parity Error

The controller detected a parity error on the host SCSI bus or one of the drive SCSIbuses.

4800 1,B

Initiator Detected Error Message Received

The controller received an Initiator Detected Error Message from the host during theoperation.



4900 B

Invalid Message Error

The controller received a message from the host that is not supported or was out ofcontext when received.

4980 BDrive Reported Reservation Conflict

A drive returned a status of reservation conflict.

4B00 1,4

Data Phase Error

The controller encountered an error while transferring data to/from the initiator orto/from one of the drives.

4E00 B

Overlapped Commands Attempted

The controller received a tagged command while it had an untagged command pendingfrom the same initiator or it received an untagged command while it had a taggedcommand(s) pending from the same initiator.

8002 4 Bad ASC code detected by Error/Event Logger

8003 4 Error occurred during data transfer from SRM host

8400 4

Operation Not Allowed With the Logical Unit in its Current State.

The requested command or Mode Select operation is not allowed with the logical unit inthe state indicated in byte 76 of the sense data. Examples would be an attempt to reador write a ″dead″ logical unit or an attempt to verify or repair parity on a ″degraded″logical unit.

8406 4 LUN Awaiting Format

8501 4

Drive I/O Request Aborted

IO Issued to Failed or Missing drive due to recently failed removed drive. This error canoccur as a result of I/Os in progress at the time of a failed or removed drive.

8700 4

Microcode Download Error

The controller detected an error while downloading microcode and storing it innon-volatile memory.

8708 4 Incompatible Board Type For The Code Downloaded

870E 6 Controller Configuration Definition Inconsistent with Alternate Controller

880A 6 Subsystem Monitor NVSRAM values configured incorrectly

8A00 5

Illegal Command for Drive Access

The initiator attempted to pass a command through to a drive that is not allowed. Thecommand could have been sent in pass-through mode or by attempting to downloaddrive microcode.

8A01 5

Illegal Command For Current RAID Level

The controller received a command that cannot be executed on the logical unit due toits RAID level configuration. Examples are parity verify or repair operations on a RAID 0logical unit.

8B02 B,6 Quiescence Is In Progress or Has Been Achieved

8B03 B Quiescence Could Not Be Achieved Within the Quiescence Timeout Period

8B04 5 Quiescence Is Not Allowed

8E01 E,6Parity/Data Mismatch

The controller detected inconsistent parity/data during a parity verification.



9100 5General Mode Select Error

An error was encountered while processing a Mode Select command.

9103 5

Illegal Operation for Current Drive State

A drive operation was requested through a Mode Select that cannot be executed due tothe state of the drive. An example would be a Delete Drive when the drive is part of aLUN.

9109 5

Invalid Action With Multiple Sub LUNs Defined

An operation was requested that cannot be executed when multiple SubLUNs aredefined on the drive.

9133 5

Illegal Operation for Controller State

The requested Mode Select operation could not be completed due to the current stateof the controller.

9136 5

Command Lock Violation

The controller received a Write Buffer Download Microcode, Send Diagnostic, or ModeSelect command, but only one command is allowed at a time and there was anothercommand active.

9150 5

Illegal Operation for Drive Group State

An operation was requested that cannot be executed due to the current state of theDrive Group.

9151 5Illegal Reconfiguration Request - Legacy Constraint

Command could not be completed due to Legacy configuration or definition constraints.

9153 5Illegal Reconfiguration Request - System Resource Constraint

Command could not be completed due to resource limitations of the controller.

9401 5 Invalid Request Due to Current Logical Unit Ownership

9501 4Extended Drive Insertion/Removal Signal

The controller has detected the drive insertion/removal signal permanently active.

9502 6

Controller removal/replacement detected or Alternate Controller Released from Reset

The controller detected the activation of the signal/signals used to indicate that thealternate controller has been removed or replaced.

9801 6The controller has determined that there are multiple sub-enclosures with the same IDvalue selected.

A000 6

Write Back Caching Could Not Be Enabled

The controller could not perform write back caching due to a battery failure ordischarge, or an ICON failure

A100 6

Write Back Caching Could Not Be Enabled - RDAC Cache Size Mismatch

The controller could not perform write back caching due to the cache sizes of the twocontrollers in the RDAC pair not matching

A400 6 Global Hot Spare Size Insufficient For All Drives In Subsystem

A600 6 Recovered processor memory failure

A700 6 Recovered data buffer memory error



C000 4,6

The lnter-controller Communications Have Failed

The controller has detected the failure of the communications between redundantcontrollers.

D006 4

Drive IO Time-out

The controller destination IO timer expired while waiting for a drive command tocomplete.

D10A 4Drive Reported Busy Status

A drive returned a busy status in response to a command.

E0XX 4

Destination Channel Error

XX = 00 through 07 indicates the Sense Key returned by the drive after a checkcondition status XX = 10 indicates that a bus level error occurred.


Appendix B. Safety Inspection Procedure

Perform a safety inspection on the system when the following conditions occur:

v The system is inspected under a maintenance agreement.

v Service is requested and service has not recently been performed.

v An alterations-and-attachments review is performed.

v Changes have been made to the equipment that might affect the safe operationof the equipment.

v External devices with an attached power cord are connected to the system unit.

If the inspection indicates an unacceptable safety condition, the condition must becorrected before you service the machine.

Note: The correction of any unsafe condition is the responsibility of the owner ofthe system.

Perform the following checks:

1. Ensure that the stabilizer is firmly attached to the bottom front of the rack.

CAUTION:The stabilizer must be firmly attached to the front of the rack to preventthe rack from turning over when the drawers are pulled out of the rack.Do not pull out or install any drawer or feature if the stabilizer is notattached to the rack.

2. Check the covers for sharp edges and for damages or alterations that exposethe internal parts of the rack.

3. Check the covers for a proper fit to the rack. They should be in place andsecure.

4. Open the rear door of the rack.

5. Switch off power to all devices (controllers, device drawers, hubs) that areconnected to the PDUs.

The controller module and device drawers have redundant power supplies. Besure to switch off power to both power supplies.

6. Unplug the device power cables from the electrical outlets on the PDUs.

7. Check for alterations or attachments. If there are any, check for obvious safetyhazards such as broken wires, sharp edges, or broken insulation.

8. Check the internal cables for damage.

9. Check for dirt, water, and any other contamination within the rack.


10. Check the voltage label on the back of the system unit to ensure that itmatches the voltage at the outlet.

11. Check the external power cable for damage.

12. With the external power cable connected to the system unit, check for 0.1 ohmor less resistance between the ground lug on the external power cable plugand the metal frame.

13. Using the appropriate probe, check for 0.1 ohm or less resistance between themetal frame and the grounding pin on each of the power outlets on the powerdistribution unit (R1, R2, R3, ...).

14. Check for the following conditions for each device in the rack:

a. Check for damage to the power cord.

b. Check for the correctly grounded power cord.

c. Check for 0.1 ohm or less resistance between the building ground and thedevice power supply enclosure.

d. With the power cord connected to the device, check for 0.1 ohm or lessresistance between the ground lug on the power cord plug and the devicepower supply enclosure.

e. For devices with removable power supplies (such as the controller moduleand the device drawer), remove each of the power supply enclosures fromthe device chassis and verify that all screws are installed and tight.

f. Replace any power supplies that were removed, and reconnect the powercables to the PDUs.

15. Switch the power on as follows:

a. Ensure the power cables of all the rack devices are plugged into theoutlets on the PDUs.

b. Ensure the power cable for each PDU is plugged into the customer’spower cable or outlet.


c. Switch the power on to the devices in the rack in the following order:

1) Device drawers

2) Controller module

d. Close the rear door of the rack.

Appendix B. Safety Inspection Procedure 271

Appendix C. Safety Inspection Procedure in German


Appendix C. Safety Inspection Procedure in German 275

Appendix D. Safety Inspection Procedure in TraditionalChinese


Appendix D. Safety Inspection Procedure in Traditional Chinese 279

Appendix E. Fibre Channel RAID Storage Server andExpandable Storage Unit Parts Catalog


2102 Model F10 Controller Module FRUs

Figure 114. 2102 Model F10 Controller Module FRUs


Figure 115. 2102 Model F10 Controller Module FRUs – cont.

Appendix E. Fibre Channel RAID Storage Server and Expandable Storage Unit Parts Catalog 283

Table 52. 2102 Model F10 Controller Module FRUs

ID NumberPart Number(P/N)

Description

1 REF 10L6981 Controller Module Chassis Assembly

1 09L1301 Controller Module Backpanel/Card Cage

2 01K6740 Controller Module Fan

3 01K6742 Controller Module Battery Assembly

4 10L6993 Controller Module 32/128MB Controller Canister

Figure 116. 2102 Model F10 Controller Module FRUs – cont.


Table 52. 2102 Model F10 Controller Module FRUs (continued)


Description

4 09L1111 Controller Module 32/256MB Controller Canister

5 10L7043 Controller Module Bezel Assembly

6 01K6743 Controller Module Power Supply

7 01K6741 Controller Module Power Supply Fan

15 03K9281 Controller Module 5V Fan Cable

16 03K9284 Controller Module 12V Power Supply Cable

17 03K9285 Controller Module Battery Cable

18 03K9280 Controller Module Media Interface Adapter

19 03K9202 5 Meter FC Host Cable

19 03K9204 25 Meter FC Host Cable

20 10L6983 Controller Module Rail Kit

30 05H9742 WTI DATA APS16 Switch

31 05H9744 150 foot WTI RJ-45 Cable

32 08L7980 WTI LDRJ-9FNL Connector

33 05H9745 WTI LDRJ-9F Connector

34 05H9044 Microcom Deskporte Fast Modem

35 08L8045 Laptop Null Modem Cable

1 01K6739 Controller Module Miscellaneous Hardware Kit¹

¹Controller Module Miscellaneous Hardware Kit:

v Nut clips (2)

v Controller latch levers

v Power supply latch lever

v Screw M6x16L

v Miscellaneous screws

v Bezel Ball Studs (2)

v Bezel Stand Off (2)


2102 Model D00 Drive Module FRUs

Figure 117. 2102 Model D00 Drive Module FRUs


Table 53. 2102 Model D00 Drive Module FRUs


Description

41 01K6706 Drive Drawer Fan

43 01K6708 Drive Drawer ESM Module

42 01K6709 Drive Drawer Power Supply Module

40 09L1119 Drive Drawer Chassis/Midplane

47 09L1118 Drive Drawer Front Bezel

not pictured 01K6671 Drive Drawer Miscellaneous Parts¹

44 01K6689 Drive Drawer Mount Hardware (left/right rail assembly)

48 03K9196 2M SCSI Device Cable

45 09L1199 4.5 GB SCSI HDD Assembly (w/ tray)



46 01K6677 Blank Drive Tray with holes (includes bezel)

¹Drive Drawer Miscellaneous Parts:

v EMC clips (6)

v HDD tray spring clip

v HDD tray fastener

v Tray mounting screws (2)

v light pipes (2)

v Left ESM latch lever

v Power supply latch lever

v ESM latch lever screw (2)

v Power supply lever screw

v Power cord clamp

v knurled nut

v screw M8 long slotted flat head (2)

v screw M6 (2)

v spacer locating

v screw; 6–32 1/2 inch length

v shipping box


Glossary

ACE – Array Configuration Editor.

battery FRU – a removable unit that contains batteries and battery charger circuitry.

battery harness – a ribbon cable that provides a power connection between thebattery FRU and the controller backpanel.

connector plate – a protective panel that contains access holes for interfaceconnectors and jumpers.

controller backpanel – a circuit board that provides interface and powerconnections between the components inside the chassis (controllers, powerinterface board, and fans), as well as to LVD-SCSI drives and to devices on theFibre Channel network.

controller card cage – a modular structure inside the chassis consisting ofcontroller shelves and the controller backpanel.

controller FRU – a removable unit that contains an array controller.

controller fan FRU – a removable unit that contains two cooling fans.

controller slot – an opening on the front of the controller module that holds acontroller FRU.

controller slot letter – identifies the physical location of the controllers in thecontroller module chassis.

cooling system – components, including controller fans, power supply fans, and airvents, that aid in air circulation and cooling within the controller module’s chassis.

ESM – Environmental Services Module.

FRU (pronounced “frew”): Field Replaceable Unit. – Removable, portable canistersthat house controllers, batteries, power supplies and fans.

DIMM – Dual Inline Memory Module.

DRM – RAID Manager for DOS.

drive SCSI ID – numbers that identify each controller to the LVD-SCSI drives.

Fibre Host ID – numbers that identify each controller to the host or other deviceson the Fibre Channel network.

front cover – a removable panel with holes for viewing the status lights and forboosting air circulation.

hot swapping – a feature that allows you to replace a component while thecontroller module is powered-up and running.

LEDs (Light Emitting Diodes) – green or amber lights that glow or blink to indicateeither a normal operating status or hardware error.


LUN – Logical Unit.

LVD-SCSI – Low Voltage Differential – Small Computer System Interface.

MIA (Media Interface Adapter) – a device that allows you to connect fiber opticcable to a copper wire connector.

power interface board – a circuit board that provides electrical connectionsbetween the power supplies and other components in the chassis.

power harnesses – provide power connections between the power interface boardand the controller backpanel.

power supply assembly – a modular structure inside the chassis consisting of thepower interface board and slots for holding the power supply and power supply fanFRUs.

power supply FRU – a removable unit containing a power supply.

power supply fan FRU – a removable unit containing fans for cooling the powersupplies.

power system – components, including batteries, power supplies, power harnessesand cords, and a power interface board, that supply electricity to the controllermodule and its components.

RAID – Redundant Array of Independent Disks.

redundant pair – two controllers attached to the same host.

SIMM – Single Inline Memory Module.

Storage Management Software – refers to the Fibre Channel Storage Managersoftware and associated components (specifically Configuration, Maintenance andTuning, Status and Recovery applications in Fibre Channel Storage Manger forWindows NT, HP-UX and Sun Solaris and RAIDiant Disk Array Manager in FibreChannel Storage Manager for AIX).

support rails – hardware used to mount a controller module chassis into arackmount cabinet.

UPS – Uninterruptible Power Supply.

VHDCI – Very High Density Cable Interface.


Index

Special Characters+12 V signal 195+5 V signal 195, 196

Numerics16-bit

cables 194drives 143, 159interface 193

18 GB drives 141, 143, 159, 1924.5 GB drives 141, 1434 GB drives 159, 19250-pin

cables 19468-pin

cables 1949 GB drives 141, 143, 159, 192

AA (ampere) 39AC

power cord routing 41voltage

power supply 118specifications 39

AC voltageconversion of 149requirements 39See also electrical, power, connector, or switch 197

accessdrive module from host 148hole in front panel 144to FRUs 72

ACK (acknowledge) signal 194, 195active current sharing 150Active LED

drive FRU 143, 157, 197Active LED on drive FRU 196ACTIVE_LED signal 195, 196activity

controller FRU 77in cache memory 76

adapterhost 35, 87MIA 42

addressing host through software 42air

circulation 38, 103flow 38, 102, 144, 151, 187illustration of flow 102proper ventilation 101vents 101, 144, 151, 187

front cover 69alarm signal 148algorithm for Fibre addresses 42altitude specifications 38

amber lightsbattery FRU 77controller fan FRU 76controller FRU 77drive FRU 143, 197ESM FRU 147, 197fan FRU 151, 197front cover 76power supply fan FRU 78power supply FRU 149, 197

ambient air temperature 171, 187See also drive module, installing 187

amperage requirements 39ampere (A) 39anti-electrostatic protection 159arbitration 195array controllers 87assembling/disassembling chassis 83ATN (attention) signal 194, 195automatic

power recovery 40

Bback cover

illustrated 72removing 72

back view of controller module 70back views of drive module 143backpanel 96basic drive module components 142batteries 69battery

leaking 118life expectancy 112recycling 118See also battery FRU 124status signals for 124

battery charger 69battery FRU

accessing 46, 72battery harness problems 125checking service date 115damaged 118described 69, 112illustration of 113in controller 149in power system 111labels 115LEDs 77life expectancy 112, 115location of 69power harness for 123precaution on servicing 114problems with 113removing 116replacing 116service label 113


battery FRU (continued)servicing notes 46specifications 113troubleshooting problems 114warranty 114

battery harnessconnecting/disconnecting 84description 123illustration of 124replacing defective 125service notes 124specifications 124troubleshooting 125

binary-coded digital (BCD) 191bits for VUPT 148blank panel 44blocks of data 193board

controller backpanel 96power interface 111

Bridge Enable switch 48BSY (busy) signal 194, 195, 196bus device ID 195

CC/D (command/data) signal 194, 195, 196cabinet

drive moduledimensions 38

illustrated 69mounting rackmount chassis into 48preparing for installation 44rackmount

preparing 43removing drive module from 174styles of 69

cableconnections 41, 49, 72copper wire 42drive 81Ethernet 49examples of connecting to drives 59fiber optic 42Fibre Channel 42, 87handling precautions 48, 82, 94interface 82length 42LVD-SCSI requirements 42overview of 41precautions for Fibre Channel 81RS-232 49SCSI 87, 88SCSI drive 87See also battery harness, DC power harness, and

power cord 72troubleshooting 87VHDCI 42

cablesconnecting to

SCSI 53disconnecting SCSI 174

cables (continued)problems with 53SCA-2 drive 195SCSI 42

P-cable 194pin assignments 194

See also Ethernet, power cord, RS-232, or SCSIcables 169

servicing notes 169specifications for 194

cache memory 91, 191, 193battery backup 112fast write indicator 76power backup for 112See also memory, DIMMs, and SIMMs 76

capacitydrive 143, 145, 159, 192non-RAID drives 145number of drives 144of drive module 141

captive screw 106Caution label 185Celsius (oC) 38changing

cable connections 53controller module 78drive SCSI ID settings 51factory default settings 191host SCSI ID settings 51options 51temperature 38

channel (drive)bus 1 191bus 2 191numbers 192SCSI ID settings 191

channel numbers (drive) 144, 148charge

+12 V 195, 196+5 V 195, 196

chassisair circulation 103air flow 102assemble/disassemble 83front mounting flange 176mounting rackmount 48rackmount removal 82temperature restrictions 148ventilation holes 101

checkingbattery FRU 115communication problems 169drive FRU LEDs 157drive module status 156ESM FRU LEDs 158fan LEDs 158for controller failure 94power supply LEDs 158presence of FRUs 148shutdown sequence 74site preparations 36


checking (continued)software status 115, 169startup sequence 73temperature in chassis 148

circuit boardcontroller backpanel 96power interface 111

circuit board interface 142See also controller FRU, ESM FRU, and

mid-plane 142circuit breaker 40communication system 168condensation 39configuration 145

drives 58incorrect settings 168of controller module 58of software 56setting interface options 51software tools for 192storage capacity 145

connectingbattery harness 84DC power harnesses 83power cords 56power cords to

drive module 53connector

controller backpanel 97controller FRU 89, 90external 87interface 72locations of 41power 72protection for 70

connector plate 41, 70connectors

AC power 197drive FRU 159ESM FRU 147mid-plane 148power 149, 197SCSI 147, 197See also drive module, installing 153types of 153

control logic 147controller

checking for failure 94data transfer rates 91factory settings 91host connections per 91host ID 89interface 91redundant pair 91See also controller FRU 93

controller backpanel 87described 96location of 71removing/replacing in chassis 85replacing failed 98servicing notes 97

controller backpanel 97 (continued)specifications 96troubleshooting 97

controller fan FRUaccessing 46, 72described 69, 103hot swapping 105LEDs 103location of 69overall cooling system 101replacing failed 106servicing notes 105specifications 104time limit for replacing 105troubleshooting 105

controller FRUaccessing 46, 72battery

backup 149cooling fans for 103default settings 42described 69, 89Fast Write Cache indicator 76fault indicators

front cover 76, 93FRU 76, 93

host ID 42, 89hot swapping 91installing/removing 95LEDs 75, 89lever 89location of 69, 87, 89memory 76

battery support of 112number of 89parts 89problem indicators 93problems with 168replacing failed

controller 93servicing notes 91shelves for 71slot numbers 89software addresses for 42specifications 91troubleshooting 92

Controller LEDcontroller fan FRU 76front cover 76

controller moduleair flow 38, 102altitude requirements 38back and front covers 72back view 70cabinet styles 69cables and connectors 41chassis disassembly 83checking software status 89circuit breaker requirements 39connecting to

drive modules 48

Index 293

controller module (continued)host 38

cooling system 101cover plate 83data transfer rates 91dimensions 37drive cable connection examples 59electrical overload protection 40features 69Fibre host ID

switch 42switches 41via software addresses 42

front view 69FRUs 79host connections 91host ID 42humidity 39ID numbers 89initial start-up 56initial startup 73installation 35interface boards 87interface connectors 41, 49, 89items shipped with 45maintaining 87, 88making changes to 78maximum drives supported 91memory 91mounting rackmount on rails 48operating 72overheating 119power

cords 41, 57, 111harnesses 83requirements 39supplies 118switch 57, 72, 73system 111

power-up sequence for 56preparing

for installation 45for move 79rackmount cabinet 44

removing fromrackmount cabinet 81

setting host ID 55shipping contents 45shutting down 74site requirements 36software configuration 58space requirements 36start-up notes 56support rails 82temperature and humidity 38turning off power 74turning on power 72voltage specifications 39weight 36wiring for 39

controller slot number 89

controllinghow drives spin-up 191information on bus 196

coolingproblems with 148, 187, 188system 151, 187

cooling system 101controller fans 69for power supplies 70illustrated 101servicing 101troubleshooting 102

copper wire 91cable length 42cable specifications 42connector 41, 42

cover plate removal 83current 39current requirements for drive module 39customer replaceable units (FRUs) 144

Ddamage

fire or flood 155data

blocks 193bus 195controlling movement of 196dumping from cache memory 191loss due to

damaged cables 48loss due to magnetic fields 159parity 195preventing loss of 160protection during power outage 112protection with UPS 191reconstruction 163, 193redundancy 193transfer handshake 195transfer rates 91

copper wire 42fiber optic 42

transmission error 93, 171writing to drive 193

data storagearea 192cache memory 191, 193capacities 145logical vs. physical 192preparing for 193redundant 141, 192

DB(0-15) (data bus) signals 195DB(P) (data bus parity) signal 195DC power harness

connecting/disconnecting 83described power

harnesses 126illustration of 127replacing failed 128specifications 127troubleshooting 127


DC voltagepower supply 118requirements 39

DC voltage in power supply 149default settings 42, 58, 91

drive SCSI IDs 144power switch 191preset at factory 193software parameter 192, 193table of switch settings 191

degrees (o) 38delay

during data reconstruction 193signal for drive spin-up 196start 191timing for spin-up 196

detectingdrive module FRUs 148

detecting errors 75, 87determining fan failures 102device ID 191dew point 39diagnostic cables and interface 49, 91differential 141, 147, 192, 193DIFFSENS (differential sensor) signal 194dimensions 37, 38dimensions of drive module 37DIP switch 191disk array 141, 168, 169, 192, 193DLYD_START (delay start) signal 195, 196domestic voltages 39drive

16-bit 143activity

error 168indicator 143, 157, 197removing FRU during 160

activity at power off 74bridge enable switch 48cable connectors for 41, 49, 96cable routing examples 59

rackmount 59cache memory dumps to 191capacity and size 141, 143, 145, 192channel numbers 144, 145, 148, 192channels 91checking status of 157circuitry 159configuration 58connecting to controller module 48data segments 193data transfer rate to 91delay start 191, 196described 143, 146detection of 148failure/fault

indicator 143, 197multiple failures 161on SCSI bus 168replacing FRU 161

group 193

drive (continued)hot spares 143ID numbers 145, 147, 148, 172, 191, 192ID signals 196identify command 143, 148, 164interface 91logical 192marked as failed 159maximum supported 91Option switch 197per drive module 141, 159, 192physical location 192problems with 160reconstruction

after failure 163reconstruction parameters for 193remote start 191, 196SCA-2 pin assignments 195SCSI ID number 42SCSI interface 141, 147See also channel (drive), SCSI ID, drive, and default

settings 145setting drive ID 145, 147, 172, 191signal 196slot 144, 160spin-up

delay 191signal 196

spindle synchronization 196status indicators 143turning on before controllers 56, 73types of 143, 159UPS supported 191

drive FRU

activity indicator 157, 197checking status 157components 197cooling of 151described 142, 144fault indicator 197handling and protection 159hot plugging 196ID numbers 145installing/removing

during drive activity 160from drive module 162, 175notes on 159

LEDs 143, 157, 197lever 143, 144, 197location of 142, 145locking bar 143mid-plane connections 148power indicator 197replacing

a failed 160in correct slot 160

SAF-TE chip monitoring 147See also channel (drive), SCSI ID, drive, and default

settings 145sizes 143, 159

See also capacity 159

Index 295

drive FRU (continued)slots 157troubleshooting 160

drive LEDs 143

Drive Module 141, 142, 143

drive module

capacityof drives 145

Caution label 185chassis mounting holes 176checking

hardware status 156software status 169through host 148

communication system 168connecting cables 53connectors 153continuous operation of 155cooling system 151, 187default settings for 191described 141dimensions 38emergency shutdown 155error detection 147features

hardware 192software 192, 193

front panel 143, 197handles and levers 153host controller for 192IDs

drive SCSI ID 147tray ID 147

LEDs See LED 149linking multiple 147monitoring status of 147mounting in cabinet 49number

IDs 192of drives 192

overheating of 170parts

back 197front 197illustration 142, 143mounting screws 177overview of 142

powerconnector 149, 197restoring 156switch 149system 149

power-up sequence 153, 156removing

from cabinet 174FRUs 175

SCSIID numbers not used 191interface 197

SCSI components 146

drive module (continued)See also SCSI, SCSI bus, SCSI cables, SCSI ID,

or SCSI interface 145Drive Module

See also drive module 142drive module

servicingdrives 161ESM FRU 170fans 188mid-plane 173power supplies 183

settingtray ID 191

status indicators 153storage capacity 192switches

Option 147, 197Power 197Tray ID 147, 197types of 153

technology used 192tray ID 192turning power

off 154on 153

UPS support 191user interface 192

drive SCSI IDin VUPT byte 148not used by drive module 191numbers 145, 192precautions for setting 172setting 145, 147signals 196switch 197

dual fans 103

Eearth ground 40electrical

ACconnector 197switch 197

circuit breakers 39, 40controller module requirements 39copper wire signal 42current 39diagnosing problems 180earth ground 40frequency 39operating current 39overload protection 40plug on power cord 39power cords 118receptacle 39single-phase wiring 40site wiring 39specifications and requirements 39surges 155voltage interruptions 40


electrical (continued)voltage requirements 197

electrolyte gel 118electrostatic discharge (ESD)

drive FRU 159ESM FRU 167mid-plane 167

emergency shutdown procedure 155Enclosure Temperature Alert (ETA) bit 148environmental

conditions 147problems with heat 171requirements 147sensors 147

environmental requirements 38equipment

See also tools 159service

drive FRU 161ESM FRU 170fan FRU 188grounding strap 159mid-plane 174power supply FRU 183SCSI cables 169

equipment needed for installation 35error

battery low 114configuration settings 168controller fault 92data transmission to drives 160, 165detection via ESM FRU 147drive 143, 159ESM FRU 170FC transmission 93host operating system software 168I/O 160, 165, 168, 173indicators for 153over-temperature 148power switch 149SAF-TE chip detection 147SCSI bus transmission 93, 171See also troubleshooting 93software application 168

ESM FRUconnectors 147described 146drive-related problems 164failure 170features of 192function of 147I/O transmission problems 168illustration 147installing/removing 172latch 173LEDs 147, 153, 158lever 146, 197mid-plane connections 148opening handles 173parts 146, 197preparing replacement FRU 172

ESM FRU (continued)problems with 147pull rings 173replacing a failed 170SAF-TE chip 147SCSI connections 147servicing notes 167slot 147software error 171switches

Option 145, 147, 172, 197Tray ID 147, 197

tray ID number 192unlocking 173who may service 167

Ethernet 91connecting cable 49connector 41

exhaust for cooling 151

Ffactory default settings 42, 58, 91, 191, 193Fahrenheit (oF) 38failure/fault

battery FRU 116controller FRU 76, 168DC power harness 128drive FRU 143, 159, 161drive-related 161, 165, 168ESM FRU 168, 170fan FRU 158, 188fan indicator 103fans 76, 78, 102host adapter board 89, 168, 169indicator 143, 147, 149, 151, 153, 156, 197indicators 76interface cables 168lines 148mid-plane 168, 173, 174on multiple drives 161overheating 158, 170power supply 122power supply FRU 76, 150, 158, 183temperature 148

fandetermining which failed 102fault LED on front cover 76

fan FRUchecking status 158components 197described 142, 151detection of 148failure 188fans per FRU 151function of 187handle 151hot swapping 187illustration 151installing/removing 175, 189interchanging units 187latch 151

Index 297

fan FRU (continued)LEDs 158, 158location of 142, 151mid-plane connections 148motors not running 188orientation in chassis 151replacing a failed 188SAF-TE chip monitoring 147See also controller fan FRU, cooling, or power

supply fan FRU 70servicing notes 187slot 151

Fan LEDcontroller fan FRU 76front cover 76location of 103troubleshooting with 102

Fast Write Cachechecking before shutdown 74LED

described 76operation during I/O 75

Fault-A LED 77Fault-B LED 77Fault LED

battery FRU 76controller FRU 77drive FRU 143, 197ESM board (over-temp) 158fan FRU 151, 158, 197front cover 76over-temperature 148power supply fan FRU 78power supply FRU 149, 158, 183, 197

features of drive modulehardware 192software 192, 193

fiber optic cable 91handling precautions 81length 42specifications 42

Fibre Channelcable

connections 35, 49handling precautions 81proper handling of 48requirements 42

connections 41controllers 87, 89copper wire 42data transfers 42host

adapters 87connections 89ID 41, 42, 88

hub 87interface connector 41MIA 42setting host IDs 55switch 87

Fibre Channel Storage Manager 192

Fibre host IDnumber 42setting 55software addresses for 42switch 42

field replaceable unit (FRU) 148See also mid-plane 146

field replaceable units (FRUs) 69See also battery FRU, controller FRU, controller fan

FRU, and power supply FRU 69fire or flood precautions 155flanges on front of chassis 176front cover

depth of 37, 38described 69illustrated 72LEDs 69, 76Power Supply LED 122removing 72

front panel 143, 197described 142illustrated 144LEDs 142, 143, 197

front panel dimensions 37front view of controller module 69front view of drive module 142Full Charge LED on battery 77fuse requirements 39

Ggaining access to FRUs 72gigabyte (GB) 39GND (ground) signal 194gradient (humidity) 39green lights

battery FRU 77controller fan FRU 76controller FRU 77drive FRU 143, 197ESM FRU 147, 158, 197front cover 76power supply fan FRU 78power supply FRU 78, 149, 158, 197

ground wiring 40grounding strap 159grouping drives 145, 193

Hhandling Fibre cables 81handshake 195hardware

interface problems 168See also battery FRU, controller FRU, drive FRU,

ESM FRU, fan FRU, midplane, power supply FRU,and drive module 180

hardware failuredetection by SAF-TE chip 147drive FRU 143, 161, 197drive-related 165, 170, 173due to overheating 147, 170, 197


hardware failure (continued)ESM FRU 147, 197fan FRU 151, 188, 197mid-plane 173power supply FRU 149, 183, 197power system 155, 180

harness 111hazardous conditions 155hazardous waste 118Heartbeat LED 75, 77heat problems with drive module 171heating and air conditioning 38hertz (Hz) 39holes for air circulation 101host 147

adapter 35, 87attaching to several 147cable connections to 35command to drive 143connecting to 193connections 89, 91control of LEDs 147data transfer rate to 91drive errors 164drive spin-up command 196installation of 35interface 91, 141LED control of drives 147multiple 141operating system 168polling for status 148SCSI-3 interface 193software address 42tray ID for drive module 192

host adapterfailure of 169problems with 168

host controller 192error reporting to 147marking drives as failed 160spin-up command 196

host IDbased on software address 42controllers 89default setting 91factory settings 91number assignments 42setting 55switches 41

host SCSIconnector 197IN/OUT connectors 147interface 192signal descriptions 195

host SCSI IDnumbers 145setting 51

hot plugging 196hot spare 192hot swap 118Hot Swap 141, 150, 151, 187, 192

hot swapcontroller 91controller fan FRU 105power supply fan FRU 109

how toavoid data loss 172check

drive LEDs 157drive module status 156ESM FRU LEDs 158fan FRU LED 158power supply LEDs 158

connect interface cables 53diagnose problems

drive FRU 160drive-related 165ESM FRU 170mid-plane 173

disconnect SCSI cables 171install/remove

ESM FRU 173fan FRU 190power supply FRU 186

perform an emergency shutdown 155prepare

new ESM FRU for installation 172prepare cabinet for controller module 43prepare cabinet for drive module 43replace a failed

drive FRU 161ESM FRU 170fan FRU 188mid-plane 174power supply FRU 183

turn off the power 154turn on the power 153

hub 42, 87humidity specifications 39Hz (hertz) 39

II/O (input/output)

activity 75, 143, 197error 160, 165, 168, 170, 173intermittent or no activity 168problems with 87stopping before shutdown 74transmission problems 168

I/O (input/output) signal 194, 195, 196identifying

driveby ID numbers 145failures 161related problems 165

ESM FRU failure 170fan failures 188mid-plane failure 173power supply failures 183

idle current 39IN/OUT SCSI connectors 147in-place signal 147, 196

Index 299

initial start up of controller module 73Initiator 194input transient 40inserting/removing FRUs 80, 81inspection 269installation

completing 56host adapters 35host interface connections 193overview of process 35preparation tasks 35preparations for 36preparing for

controller module 45rackmount cabinet 44

tools and equipment needed for 35installing/removing

drive FRU 162, 175notes on 159precautions for 160

drive modulefrom cabinet 174, 176FRUs 175

ESM FRU 172failed

drive FRU 160ESM FRU 170fan FRU 188power supply FRU 183

fan FRU 175, 189how to 190illustration 190

power supply FRU 175, 186how to 186illustration 186

interconnect board 148interface

boards 142cables

illustrated 82shipped with unit 45

connector 41, 49, 72controller 91description of boards 87diagnostic 91drive 91, 141ESM FRU and mid-plane 147external connections 87host 91, 141internal boards 87options 147, 153overview of connectors and cables 41power interface board 111problems 87, 168SAF-TE chip 147SCA-2 195SCSI

connector 148, 197differential 192

troubleshooting hints 88user 192

interface (continued)VHDCI 142

internal view of controller module 70international voltages 39

Llabel

adding to SCSI cables 171Caution on drive module 185

label on battery FRU 113, 116leaking battery 118LED

battery FRU 77behavior during I/O activity 75behavior during power-up 153, 156, 157checking status of 156controller fan FRU 76controller FRU 76, 89defined 72drive FRU

Active 143, 157, 197checking 157Fault 143, 197illustrated 144location of 143Power/Fault 197

ESM FRUchecking status 158location of 153Over-Temp 141, 147, 158, 197Power 147, 158, 197

fan FRUchecking 158Fault 151, 158, 197location of 153

flashing 75, 157front cover 69, 76front panel 142, 143on back of controller module 78on front of controller module 76power supply fan FRU 78power supply FRU 78, 122

checking 158exception to fault 183Fault 149, 158, 197location of 153Power 149, 158, 197

status table 76, 78types on drive module 153using to check status 56

length of cables 42length of SCSI cables 194lever/latch

drive FRU 143, 144, 197ESM FRU 146, 173, 197fan FRU 151power supply FRU 149, 186, 197switching on power supply 185uses for 153

light emitting diodes 72light emitting diodes (LEDs) 143


lights 72, 143, 197locking bar

access hole 144location of 143

logical units (LUNs) 193LP SCSI drives 143, 159LVD SCSI drive 91LVD-SCSI drive

cableconnectors 41, 49requirements 42

cabling examples 59rackmount 59

ID numbers for 42

Mmagnetic fields 159maintenance

battery FRU 180maintenance of battery FRU 112, 113Mated (1, 2) signals 195, 196Mated Ground signal 195maximum operating current 39media interface adapter (MIA) 42memory 191, 193

battery backup for 112cache 91Fast Write Cache indicator 76processor 91

mid-plane 147connections to

FRUs 148described 148drive

connectors to 148numbering scheme 145related problems 164

failure 168, 174fan connections to 151location of 148power

outage 155problem indicators 173replacing a failed 173, 174servicing notes 167troubleshooting 173who may service 167

missing FRUs 147module in RAID software 193monitoring drive module status 147mounting

drive module in cabinet 49MSG (message) signal 194, 195multi-mode 42multiple drive module connections 141, 147

Nnominal voltage 39non-RAID

capacities 145

numberdrive

channels 144SCSI IDs 144

drive module IDs 192host SCSI ID 144SCSI IDs 191See also drive module, installing 144Tray ID 144tray ID 191, 192

number ofcontroller slots 89days battery will maintain power 112power harnesses in unit 111

Ooperating

current 39drive module continuously 155environment 38instructions 153status indicators 153system software 169, 192temperature range 171the controller module 72

optiondrive module interface 153precaution for setting 172settings 51switch 145, 147, 197

Option switch 147or-tied signal 196Over-Temp LED

ESM FRU 147, 197feature 141

overheatingcaused by obstructed air flow 101detection 147due to fan failure 109indication of 147, 170, 171, 197power supply 119prevention with fans 103troubleshooting problems 92, 133

PP-cable

connections 194pin assignments 194

parameters in software 193parity 195parts

air vents 151cabinet styles 69controller module 69, 70drive FRU 143, 197drive module

back of 197front of 197overview of 142

Index 301

parts (continued)ESM FRU 151, 197fan FRU 151, 197front panel 144in cooling system 151in power system 149interface connectors 146locking bar access hole 144mid-plane 148power supply FRU 149, 197SCSI components 146

pin assignmentshost SCSI cable 194SCA-2 interface 195See also drive module, installing 148signals for 194VUPT byte 148

powerbattery 112, 113connector 72, 149, 197delay before turning on 181, 184drive spin-up when applied 196emergency shutdown 155factors and efficiency 39failure

and recovery 156, 192of FRU 183

for cache memory 112fuse requirements 39harnesses 123indication of 76, 77, 78, 147, 149, 158, 197

Power LED 77interface 148intermittent loss to controllers 127interruptions of 40loss and data protection 191loss and recovery 40, 119, 121outage 155overload protection 40redundancy 118redundancy of 150requirements

battery 113battery harness 124controller 91controller backpanel 97controller fan FRU 104DC power harnesses 127power interface board 130power supply 119power supply fan FRU 108

start-up notes 56system described 111troubleshooting problems with 127, 131turning off 74, 154turning on 72, 153unexpected loss of 155

power cord 149connecting 56, 57connecting/disconnecting 53, 174connector on drive module 149

power cord 111 (continued)number of 56per power supply 179used with power supplies 150with power supply 118

power harnessin power system 111servicing notes 127

power interface board 118described 130overall power system 111replacing failed 131servicing notes 130specifications 130troubleshooting 131

Power LEDcontroller fan FRU 76controller FRU 77drive FRU 197ESM FRU 147, 158, 197front cover 76power supply fan FRU 78power supply FRU 78, 149, 158, 197

power supply assemblydescribed 71, 130illustrated 96, 130overall power system 111servicing notes 130specifications 130

power supply fan FRUaccessing 46, 72described 70, 107hot swapping 109illustrated 108LEDs 76overall cooling system 101replacing failed 109servicing notes 109specifications 108troubleshooting 109

power supply FRUaccessing 46, 72checking status 158DC power harness for 126described 70, 118, 142, 149detection of 148failure/fault 183fault indicator 183fault indicators 122illustrated 150in power system 111installing/removing 123, 175interchangeable FRUs 118interface board 118latch 186LEDs 153, 158, 183lever 149, 197location of 70, 142, 149mid-plane connections 148, 150opening handles 186overheating 119


power supply FRU (continued)parts 46per drive module 179power cords for 111Power switch 149, 197pull rings 186recovery notes 119redundancy of 118redundancy support 150replacing a failed 183replacing failed 122SAF-TE chip monitoring 147shutdown and recovery 119, 121slot 149specifications 119switch 183, 191switching levers on 185troubleshooting 120, 183turning off 154turning on 153voltages 195, 196warning light 183

Power Supply LED 122Power switch 149, 183, 197power switch

defined 72Power switch

factory default setting 191power switch

location of 73turning on and off 57, 73, 74

power system 149, 150described 179elements of 179loss of power 155maintaining 180problems with 112servicing 111

power-uprecovery sequence 40sequence 56

pre-charge for hot plugging drives 196precautions for

controller fan FRU time limits 105handling Fibre Channel cables 81

preparingcontroller module for installation 35, 45controller module for move 79for initial startup 73for shut down 74

preparing for drive module installation 35preventive maintenance 180problems

access to drive 161, 164communication 168controller-related 168cooling 148, 187data transmission 161, 164, 170detection via SAF-TE chip 147drive-related 143, 160, 164, 170ESM FRU-related 168, 170

problems (continued)fan-related 161host adapter board 89, 169I/O activity 168intermittent faults 173mid-plane 168, 173overheating 170, 188power-related 180, 183SCSI-related 168software error message

drive 161, 164fan 188

troubleshooting 198unexpected power loss 155

processor memory 91proper handling of Fibre Channel cables 48protecting data during power loss 191protecting drive module in an emergency 155protocol for SCSI drive cables 42pull rings on

ESM FRU 172, 173power supply FRU 186

Rrackmount

blank panel kit 44cabinet

installation 49cabinet style 69cable connections 49chassis on support rails 82connecting to drives 59controllers 87dimensions 37drive module

back view 143front view 142

drive numbering 145front cover 72front panel access 163illustrated 69LVD-SCSI drive cabling examples 59power switches 154preparing cabinet 43preparing cabinet for installation 44preparing for relocation 79removing chassis from cabinet 82removing from cabinet 81removing front cover 72support rail kit 44

RAIDdefined 87levels supported 91levels supported by drive module 192selecting level 193software 193technology used 192

RAID drive moduleterminology 193

Index 303

RAID leveland drive failures 161

ranks for drives 145receptacle (electrical) 39reconstruction

after drive failure 163reconstruction rate parameter 193recovering from

a power supply shutdown 119, 121drive failure 161emergency shutdown 74, 156ESM FRU failure 170fan failure 188interface problems 87mid-plane failure 174power supply failure 183

recycling battery 118redundant

cooling system 103data storage 193fans 151features of drive module 192modules 141pair of controllers 91power 73power supplies 118, 150power supply fans 107

relative humidity 39reliability 141remote

start 191, 196removing

front and back covers 72rackmount module from cabinet 81

removing/replacingcontroller backpanel 85cover plate 83failed

controller 93controller backpanel 98controller fan FRU 106

replacingbattery FRU 116defective battery harness 125defective DC power harnesses 128failed power interface board 131failed power supply fan FRU 109failed power supply FRU 122

replacing a faileddrive 160ESM FRU 170fan 188mid-plane 173power supply 183

REQ (request) signal 194, 195RESERVED signal 194RMT_START (remote start) signal 195, 196routing

power cords 41RS-232 91

connecting cable 49

RS-232 41 (continued)connector 49

RST (reset) signal 194, 195

SSAF-TE chip 148

described 147detection of FRUs 147functions of 147temperature monitor 148

SAF-TE chip SCSI ID settings 191safeguarding equipment 155safety hazard 118safety inspection procedure 269safety notices 269SCA-2 interface 195screws

for mounting drive module 177SCSI

activity 143bus transmission error 93cable

maximum length 42components 146, 149, 168connectors 197defined 141drive

cables 87drive connections 89drives 143, 159IN/OUT connectors 147interface 41

connections 148differential 192

pin assignments 194servicing notes 167signal descriptions 194, 195

SCSI Accessed Fault Tolerant Enclosure chip 147SCSI bus

bus 1 191bus 2 191connections 147connector 197conversion to differential 147default ID settings for 191device failure on 168drive

capacity 145marked as failed 159

host interface 193transmission

drive access problems 161, 164software error 171

transmitting control information 196SCSI cables

connecting 53connectors 192disconnecting 171, 174maximum length 194pin assignments 194problems with 168


SCSI cables (continued)SCA-2 pin assignments 53types and lengths 42

SCSI IDdrive 145, 148, 191drive numbers 144, 192host 145module numbers 192numbers not used by 191precautions for setting 172SAF-TE chip 191selection 147, 197setting 197setting for

controller 51SCSI_ID 0-3 signal 195, 196SCSI ID for drives 42SCSI interface

differential 193ESM FRU 147

sea level 38segment size 193SEL (select) signal 194, 195, 196sensor for temperature 148service date on battery 115service technician tasks 167, 173servicing

battery 114battery harness 125controller backpanel 97controller card cage 97controller fan 105power harness 127power interface board 131power supply 112, 131power supply fan 109power system 111

servicing a faileddrive 160drive-related component 164ESM FRU 170fan 188mid-plane 173power supply 183

settingdrive

interface options 147numbers 145

interface options 197RAID level 193reconstruction rate 193tray ID 147, 191, 197

setting Fibre host IDs 55shipping

containerdimensions 37

contents of container 45controller module 79weight 36

controller 91shock and impact 159

shortwave laser 42shutdown sequence for modules 74shutting down the drive module 155signal

+12 V 195+15 V 195, 196ACK (acknowledge) 194, 195ACTIVE_LED 195, 196ATN (attention) 194, 195BSY (busy) 194, 195, 196C/D (command/data) 194, 195, 196DB(0-15) (data bus) 195DB(P) (data bus parity) 195DIFFSENS (differential sensor) 194DLYD_START (delay start) 195, 196GND (ground) 194host SCSI 194I/O (input/output) 194, 195, 196in-place 196Mated (1, 2) 195, 196Mated ground 195MSG (message) 194, 195not used 196REQ (request) 194, 195RESERVED 194RMT_START (remote start) 195, 196RST (reset) 194, 195SCSI 195SCSI_ID0-3 195, 196SEL (select) 194, 195, 196SYNC+ (synchronize spindle) 196TERMPWR (terminator power) 194

signal to verify presence of FRUs 147single-ended (SE) 141, 147single-phase wiring 40site

preparations 36site preparation

electrical wiring 39requirements for 36service area 36

sizedata segments 193drive storage capacities 145

slot numbers for controllers 89Small Computer System Interface (SCSI)

See SCSI 141software

assigning Fibre Channel addresses 42battery error 114configuration tasks 56configuration tools 192default settings 58drive identify command 143error

ESM FRU 171I/O operations 161, 164, 168over-temperature 188power supply 183SCSI transmission 171

features of 192

Index 305

software (continued)Fibre Channel Storage Manager 42interface problems 168modifying for SAF-TE chip 148operating system 168, 192parameter settings 193RAID management 168, 193shipped with controller module 45storage management 88Storage Manager 169terminology used 193transmission error 93using to

check drive module 169using to check controller module 89

software errorinterface 88

space requirements 36spares

drive FRU 161ESM FRU 170fan FRU 188mid-plane 174power supply FRU 183SCSI cables 169

specificationsaltitude 38ampere 39battery FRU 113battery harness 124cable lengths 194circuit breaker 39controller fan FRU 104controller FRU 91copper wire cable 42DC power harness 127dimensions 37domestic and international power 39drive module

dimensions 38Fibre Channel cable 42front cover depth 37, 38humidity 39LVD-SCSI drive cables 42power requirements 39power supply fan FRU 108power supply FRU 119SAFT-TE chip 148SCA-2 pin assignments 195SCSI

cables 194pin assignments 194

service area requirements 36site requirements 36site wiring 39temperature and humidity 38weight 36

spin-upcommand from host 196control for drives 191delayed start 196

spin-up (continued)remote start 196

spindle synchronization 196standard specification 148startup sequence for modules 73status

drive module 156indicators 143, 153reporting to host 147

status LEDs 76, 78status lights 56storage environment 38storage management software 88, 93Storage Manager 169support rails 44, 48, 82surge current 39switch

AC 197bridge enable 48default settings 191Fibre host ID 42illustration of Option/Tray ID 173Option 51, 147, 172, 197power 57, 73Power 149, 191, 197Tray ID 51, 147, 191, 197types of 153

switching device for Fibre Channel 87SYNC+ (synchronize spindle) signal 196

TTarget 194technology used in drive module 192temperature

alarm signal 148ambient air 171, 187cooling in drive module 151levels of 148limitations for chassis 148monitor 148monitoring logic 103overheating in chassis 105overheating indicator 141, 170problems with power supply 119requirements 38SAF-TE chip monitoring 147

terminators shipped with controller module 45TERMPWR (terminator power) signal 194tools

Allen wrench 161hex nut driver (#6-32) 174needed for installation 35Phillips head screwdriver (#6-32) 174

tools needed for installation 35transit environment 38Tray ID

numbers 191, 192setting 51, 147, 197switch 51, 147, 191, 197using with multiple hosts 147

troubleshootingbattery harness problems 125


troubleshooting (continued)battery problems 125chart 198communication problems 169controller backpanel problems 97controller fan problems 105controller problems 92, 168cooling problems 101cooling system 187DC power harness problems 127drive

failure 160marked as failed 159

ESM FRU 168, 170fan failures 102, 105fan FRU 188hints for interface problems 88host ID problems 88I/O transmission problems 168interface problems 87

hardware 88software 88

intermittent power loss 127mid-plane 173overheating problems 92, 101, 119, 133power

supply failure 149, 183system 180

power interface board problems 131power shutdown 119power supply fan FRU 109power supply FRU 183power supply problems 120power system problems 112SCSI

cable 168interface 168

through software 89, 169unexpected power loss 155with Ethernet cable 49with RS-232 cable 49

turning off the power 74turning on

controller module 56, 72drives before controllers 56

turning the poweroff 149, 154on 149, 153See also power switch 197

UUltra SCSI cable 42ultra-SCSI interface 193uninterrupted power supply (UPS)

drive support option 191support for cache memory 191VUPT byte assignment 148

unlockingESM FRU 173fan FRU 190

unlocking (continued)power supply FRU 173

UPS_inpl bit 148user

controls 143, 153replaceable

battery FRU 180cables 167drive FRUs 160fan FRUs 187power supply FRUs 180

Vv AC (volts AC) 39v DC (volts DC) 39Vendor Unique Pass-Thru (VUPT) byte 148ventilation 171, 187vents in drive module 151VHDCI (very high density cable interface) 42voltage 149

+12 V signal 195+5 V signal 195, 196domestic and international 39drives 195, 196for hot plugging 196nominal 39precharge for hot plugging 196specifications 39

volts AC (v AC) and DC (VDC) 39

Wweight

battery FRU 113controller fan FRU 104controller FRU 91power supply fan FRU 108power supply FRU 119specification 36

wiringearth ground 40single-phase 40site requirements 39

Index 307

Readers’ Comments — We’d Like to Hear from You

Fibre Channel RAID Storage Server andExpandable Storage Unit, IBM 2102Model F10 and Model D00Service Guide

Publication No. SY27-7604-02

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very DissatisfiedOverall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very DissatisfiedAccurate h h h h h

Complete h h h h h

Easy to find h h h h h

Easy to understand h h h h h

Well organized h h h h h

Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any wayit believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.

Readers’ Comments — We’d Like to Hear from YouSY27-7604-02

SY27-7604-02

IBMRCut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

International Business Machines CorporationRCF Processing DepartmentG26/0505600 Cottle RoadSan Jose, CA 95193-0001

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

IBMR

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

SY27-7604-02

Spine information:

IBM

Fibre Channel RAID Storage ServerandExpandable Storage Unit, IBM 2102Model F10 and Model D00 IBM 2102 Model F10 and Model D00 Service Guide

service guide - ps-2.kev009.comps-2.kev009.com/rs6000/manuals/fibre/2102-f10-d00... · 1999. 12....

Documents