Compaq Computer Corporation
Houston, Texas
Service Manual
January 1999
While Compaq Computer Corporation believes the information included in this manual is correct as of date of
publication, it is subject to change without notice. Compaq Computer Corporation makes no representations that
the interconnection of its products in the manner described in this document will not infringe existing or future
patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell
equipment or software in accordance with the description. No responsibility is assumed for the use or reliability of
firmware on equipment not supplied by Compaq Computer Corporation or its affiliated companies. Possession, use,
or copying of the software or firmware described in this documentation is authorized only pursuant to a valid
written license from Compaq Computer Corporation, an authorized sublicensor, or the identified licensor.
Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are
licensed to the U.S. Government with the Compaq Computer Corporation standard commercial license and, when
applicable, the rights in DFAR 252.227 7015, "Technical Data--Commercial Items."
1999 Compaq Computer Corporation.
All rights reserved. Printed in U.S.A.
Compaq, DIGITAL, the Compaq and DIGITAL logos are registered with the U.S. Trademark and Patent office.
DIGITAL UNIX, DECconnect, HSZ, StorageWorks, VMS, OpenVMS, are trademarks of Compaq Computer
Corporation.
UNIX is a registered trademark of the Open Group in the U.S. and other countries. Windows NT is a registered
trademark of the Microsoft Corporation. Sun is a registered trademark of Sun Microsystems, Inc. Hewlett-Packard
and HPUX are registered trademarks of the Hewlett-Packard Company. IBM and AIX are registered trademarks of
International Business Machines Corporation. All other trademarks and registered trademarks are the property of
their respective owners.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15
of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the
equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio
frequency energy and, if not installed and used in accordance with the manuals, may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in
which case the user will be required to correct the interference at his own expense. Restrictions apply to the use of
the local-connection port on this series of controllers; failure to observe these restrictions may result in harmful
interference. Always disconnect this port as soon as possible after completing the setup operation. Any changes or
modifications made to this equipment may void the user's authority to operate the equipment.
Warning!
This is a Class A product. In a domestic environment this product may cause radio interference in which case the
user may be required to take adequate measures.
Achtung!
Dieses ist ein Gert der Funkstrgrenzwertklasse A. In Wohnbereichen knnen bei Betrieb dieses Gertes
Rundfunkstrungen auftreten, in welchen Fllen der Benutzer fr entsprechende Gegenmanahmen verantwortlich
ist.
Avertissement!
Cet appareil est un appareil de Classe A. Dans un environnement rsidentiel cet appareil peut provoquer des
brouillages radiolectriques. Dans ce cas, il peut tre demand l' utilisateur de prendre les mesures appropries.
Contents iii
Contents
Preface
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Electrostatic Discharge Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
VHDCI Cable Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Local-Connection Maintenance Port Precautions . . . . . . . . . . . . . . . . . . . xii
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Special Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Required Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Chapter 1 General Description
Subsystem Typical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Controller Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Policy Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Program Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Nonvolatile Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Dual UART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Diagnostic Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Maintenance Connection Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Local Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Buses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Bus Exchanger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Value-Added Functions Chip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Host Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
iv Service Manual
Device Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
HSOF Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Initialization Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Executive Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Host Interconnect Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
User-Interface Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Subsystem Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Fault Management Utility (FMU) . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Virtual Terminal Display (VTDPY) . . . . . . . . . . . . . . . . . . . . . . . . . 116
Disk Inline Exerciser (DILX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Field Replacement Utility (FRUTIL). . . . . . . . . . . . . . . . . . . . . . . . 116
Configuration Utility (CONFIG) . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
HSUTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Code Load/Code Patch Utility (CLCP) . . . . . . . . . . . . . . . . . . . . . . 117
Configuration menu (CFMENU) . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Clone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Device Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Value-Added Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Cache Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
External Cache Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Array Controllers and Hot Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Host Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Chapter 2 Troubleshooting
Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Checking Failure Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Displaying Failure Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Translating Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Instance Codes and Last Failure Codes . . . . . . . . . . . . . . . . . . . . . . 214
Controlling the Display of Significant Events and Failures . . . . . . . . . . 215
Checking for Communication Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
VTDPY Run Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Checking Controller-to-Host Communications. . . . . . . . . . . . . . . . . . . . 218
Checking Controller-to-Device Communications . . . . . . . . . . . . . . . . . . 219
Checking Device Type and Location . . . . . . . . . . . . . . . . . . . . . . . . 220
Contents v
Checking Device Status and I/O Activity. . . . . . . . . . . . . . . . . . . . .221
Checking Device-Port Status and I/O Activity. . . . . . . . . . . . . . . . .223
Checking Unit Status and I/O Activity . . . . . . . . . . . . . . . . . . . . . . . . . .224
Checking for Disk-Drive Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Finding a Disk Drive in the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . .227
Testing the Read Capability of a Disk Drive . . . . . . . . . . . . . . . . . . . . . .227
Testing the Read and Write Capabilities of a Disk Drive . . . . . . . . . . . .228
DILX Run Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229
DILX Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232
Running the Controller Self Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232
Self Test Run Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
Shutting Down and Restarting the Subsystem . . . . . . . . . . . . . . . . . . . . . . . .233
Shut Down Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233
Restart Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
Chapter 3 Replacement Procedures
Single Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Replacing the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Controller Removal Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Controller Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Replacing the Cache Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Cache Module Removal Procedures. . . . . . . . . . . . . . . . . . . . . . . . . .37
Cache Module Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . .39
Replacing the ECB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Installing a New Program Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312
Dual-Redundant Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .313
Replacing a Controller Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314
Controller Removal Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . .314
Controller Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . .316
Replacing a Cache Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319
Cache Module Removal Procedures. . . . . . . . . . . . . . . . . . . . . . . . .319
Cache Module Installation Procedures . . . . . . . . . . . . . . . . . . . . . . .321
Program Card Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324
Shutdown Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324
Rolling Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325
Replacing an External Cache Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327
vi Service Manual
Replacing the ECB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Replacing a PVA Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Replacing the PVA in the Master Enclosure (ID 0). . . . . . . . . . . . . . . . . 331
Replacing the PVA in the First (ID 2) or Second (ID 3) Expansion Enclosure
333
Replacing an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Replacing an Environmental Monitoring Unit . . . . . . . . . . . . . . . . . . . . . . . . 339
Removing an EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Installing an EMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Replacing SIMMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
SIMM Removal Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
SIMM Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Replacing a Failed Storageset Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Failed RAIDset or Mirrorset Member Removal Procedure . . . . . . . . . . 343
RAIDset or Mirrorset Member Installation Procedure . . . . . . . . . . . . . . 343
Chapter 4 Upgrading the Subsystem
Upgrading Controller Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Installing a New PCMCIA Program Card. . . . . . . . . . . . . . . . . . . . . . . . . 42
Downloading New Software Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Using CLCP to Install, and Delete, and List Software Patches. . . . . . . . . 45
Software Patch Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . 45
Software Patch Deletion Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Software Patches Listing Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . 48
Upgrading Device Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Key Points in Upgrading Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Firmware Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
HSUTIL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Upgrading to a Dual-Redundant Configuration . . . . . . . . . . . . . . . . . . . . . . . 414
Installing a New Controller, Cache Module, and ECB . . . . . . . . . . . . . . 415
Upgrading to a Multiple-Bus Failover Configuration . . . . . . . . . . . . . . . . . . 418
Installing a New Controller, Cache Module, and ECB . . . . . . . . . . . . . . 420
Appendix A LED Codes
Operator Control Panel LED Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . A1
Contents vii
Solid OCP Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A2
Flashing OCP Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A6
Appendix B Event Reporting: Templates and Codes
Template and Code Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B3
Last Failure Event Sense Data Response . . . . . . . . . . . . . . . . . . . . . . . . . B3
Multiple-Bus Failover Event Sense Data Response . . . . . . . . . . . . . . . . B3
Failover Event Sense Data Response. . . . . . . . . . . . . . . . . . . . . . . . . . . . B3
Nonvolatile Parameter Memory Component Event Sense Data Response B
4
Backup Battery Failure Event Sense Data Response. . . . . . . . . . . . . . . . B4
Subsystem Built-In Self Test Failure Event Sense Data Response . . . . . B4
Memory System Failure Event Sense Data Response . . . . . . . . . . . . . . . B4
Device Services Non-Transfer Error Event Sense Data Response . . . . . B5
Disk Transfer Error Event Sense Data Response. . . . . . . . . . . . . . . . . . . B5
Instance Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B5
Instance Codes Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B6
Instance Codes Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B7
ASC/ASCQ Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B7
Event Threshold Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B7
Recommended Repair Action Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . B7
Last Failure Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B8
Last Failure Codes Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B9
Template and Code Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B11
Glossary
Index
viii Service Manual
Figures
Figure 11 Typical Installation of an HSZ70 . . . . . . . . . . . . . . . . . . . . . . 12
Figure 12 HSZ70 Physical Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 13 HSZ70 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 14 OCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 15 Initialization Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Figure 16 Cache Module and ECB "Y" Cable . . . . . . . . . . . . . . . . . . . 118
Figure 17 External Cache Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Figure 18 Host Cabling for Single Configuration . . . . . . . . . . . . . . . . . 123
Figure 19 Host Cabling for Transparent FailoverConfigurations . . . . . 124
Figure 110 Host Cabling for Multiple Bus Failover Configurations. . . . 125
Figure 21 Structure of an Instance or Last-Failure Code . . . . . . . . . . . 214
Figure 22 Xfer Rate Region of the Default Display . . . . . . . . . . . . . . . 219
Figure 23 Regions on the Device Display . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 24 Unit Status on the Cache Display . . . . . . . . . . . . . . . . . . . . . 224
Figure 31 Single Controller Configuration . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 32 Battery Disable Switch Location . . . . . . . . . . . . . . . . . . . . . . 35
Figure 33 ECB Replacement Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Figure 34 Replacing a Program Card . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Figure 35 Dual-Redundant Controller Configuration . . . . . . . . . . . . . . 313
Figure 36 Single-Battery ECB SSB Configuration . . . . . . . . . . . . . . . . 328
Figure 37 Dual-Battery ECB SBB Configuration . . . . . . . . . . . . . . . . . 328
Figure 38 I/O Module Locations in a BA370 Enclosure . . . . . . . . . . . 336
Figure 39 Cache-Module Memory Configurations . . . . . . . . . . . . . . . . 341
Figure 310 Installing a SIMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Figure 41 Location of Write-Protection Switch . . . . . . . . . . . . . . . . . . . 43
Figure 42 Connecting Dual-Redundant Controllers to the Host . . . . . . 414
Figure 43 Connecting Multiple Bus Failover, Dual-Redundant
Controllers to the Host 420
Figure B1 Structure of an Instance Code . . . . . . . . . . . . . . . . . . . . . . . . .B5
Figure B2 Structure of a Last Failure Code . . . . . . . . . . . . . . . . . . . . . . .B8
ix
Tables
Table 11 Key to Figure 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 12 Key to Figure 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 13 Key to Figure 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Table 14 Key to Figure 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 15 Key to Figure 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Table 16 Key to Figure 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Table 17 Key to Figure 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Table 21 Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Table 22 Troubleshooting Procedures (sheet 1 of 7) . . . . . . . . . . . . . . . . .24
Table 23 Event Code Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Table 24 FMU SET Commands (sheet 1 of 3) . . . . . . . . . . . . . . . . . . . . .215
Table 25 VTDPY Key Sequences and Commands . . . . . . . . . . . . . . . . 218
Table 26 Xfer Rate Column Descriptions . . . . . . . . . . . . . . . . . . . . . . . . 219
Table 27 Device Map Column Descriptions . . . . . . . . . . . . . . . . . . . . . 221
Table 28 Device Status Column Descriptions . . . . . . . . . . . . . . . . . . . . 222
Table 29 Device-Port Status Column Descriptions. . . . . . . . . . . . . . . . . 224
Table 210 Unit Status Column Descriptions . . . . . . . . . . . . . . . . . . . . . . 225
Table 211 DILX Control Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Table 212 DILX Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229
Table 213 Data Patterns for Phase 1: Write Test . . . . . . . . . . . . . . . . . . . 231
Table 214 DILX Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Table 31 Cache Module Memory Configurations . . . . . . . . . . . . . . . . . 341
Table 41 HSUTIL Messages and Inquiries . . . . . . . . . . . . . . . . . . . . . . .412
Table 42 Key to Figure 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .415
Table A1 Solid OCP Patterns (sheet 1 of 4) . . . . . . . . . . . . . . . . . . . . . . . A2
Table A2 Flashing OCP Patterns (sheet 1 of 4) . . . . . . . . . . . . . . . . . . . . A6
Table B1 Template 01: Last Failure Event Sense Data Response Format B11
Table B2 Template 04: Multiple-Bus Failover Event
Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . B12
Table B3 Template 05: Failover Event Sense Data Response Format . . B13
Table B4 Template 11: Nonvolatile Parameter Memory Component
Event Sense Data Response Format . . . . . . . . . . . . . . . . . . . . B14
Table B5 Template 12: Backup Battery Failure Event
Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . B15
x Service Manual
Table B6 Template 13: Subsystem Built-in Self Test Failure Event
Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . B16
Table B7 Template 14: Memory System Failure Event
Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . B17
Table B8 Template 41: Device Services Non-Transfer Error Event
Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . B18
Table B9 Template 51a: Disk Transfer Error Event
Sense Data Response Format (sheet 1 of 2) . . . . . . . . . . . . . . B19
Table B10 Template 51b: Passthrough Device Reset Event
Sense Data Response Format (sheet 1 of 2) . . . . . . . . . . . . . . B21
Table B11 Instance Codes (sheet 1 of 31) . . . . . . . . . . . . . . . . . . . . . . . . B23
Table B12 Last Failure Codes (sheet 1 of 28) . . . . . . . . . . . . . . . . . . . . . B54
Table B13 Repair Action Codes (sheet 1 of 10) . . . . . . . . . . . . . . . . . . . B82
Table B14 Component Identifier Codes . . . . . . . . . . . . . . . . . . . . . . . . . B92
Table B15 Event Notification/Recovery Threshold Classifications . . . . . B93
Table B16 ASC and ASCQ Codes (sheet 1 of 3) . . . . . . . . . . . . . . . . . . . B93
xi
Preface
This book provides information and guidance for troubleshooting and servicing
the HSZ70 array controller running HSOF Version 7.3. It also provides
information and guidance for troubleshooting and servicing the cache module
and external cache battery that support the controller's operation in a storage
subsystem.
This book does not contain information about the operating environments to
which the controller might be connected, or detailed information about
subsystem enclosures or their components. See the documentation that
accompanied these peripherals for information about them.
Precautions
Use the precautions described in the following paragraphs when you are
carrying out any servicing procedures:
s Electrostatic Discharge Precautions, page xi
s VHDCI Cable Precautions, page xii
s Local-Connection Maintenance Port Precautions, page xii
Electrostatic Discharge Precautions
Static electricity collects on all nonconducting material, such as paper, cloth, and
plastic. An electrostatic discharge (ESD) can easily damage a controller or other
subsystem component even though you may not see or feel the discharge.
Follow these precautions whenever servicing a subsystem or one of its
components:
s Always use an ESD wrist strap when servicing the controller or other
components in the subsystem. Ensure that the strap contacts bare skin and
fits snugly, and that its grounding lead is attached to a bus that is a verified
earth ground.
s Before touching any circuit board or component, always touch a verifiable
earth ground to discharge any static electricity that may be present in your
clothing.
xii Service Manual
s Always keep circuit boards and components away from
nonconducting material.
s Always keep clothing away from circuit boards and components.
s Always use antistatic bags and grounding mats for storing circuit
boards or components during replacement procedures.
s Always keep the ESD cover over the program card when the card is
in the controller. If you remove the card, put it in its original
carrying case. Never touch the contacts or twist or bend the card
while handling it.
s Do not touch the connector pins of a cable when it is attached to a
component or host.
VHDCI Cable Precautions
All of the cables to the controller, cache module, and external cache
battery use very high density cable interconnect connectors (VHDCI).
These connectors have small mating surfaces that can be adversely
affected by dust and movement.
Use the following precautions when connecting cables that use VHDCI
connectors:
s Clean the mating surfaces with a blast of clean air.
s Mate the connectors by hand, then tighten the retaining screws to
1.5 inch-pounds--approximately 1/4 additional turn after the
connectors have fully mated.
s Test the assembly by gently pulling on the cable, which should not
produce visible separation.
Local-Connection Maintenance Port Precautions
The local-connection maintenance port generates, uses, and radiates
radio frequency energy through cables that are connected to it. This
energy might interfere with radio and television reception. Do not leave
a cable connected to this port when not communicating with the
controller.
Conventions
This book adheres to the typographical conventions and special notices
found in the paragraphs that follow to help you find what you're
looking for.
Preface xiii
Typographical Conventions
Convention Meaning
Command syntax that must be entered exactly as
ALLCAPS BOLD
shown, for example:
S E T FAILOVER COPY=OTHER_CONTROLLER
ALLCAPS Command discussed within text, for example:
"Use the SHOW SPARESET command to show the
contents of the spareset."
Screen display.
Monospaced
Sans serif italic Command variable or numeric value that you
supply, for example: SHOW RAIDset-name
(when being described within the text) or
set this_controller id=(n,n,n,n,) when showing
how to enter the command syntax.
italic Reference to other books, for example: "See HSZ70
Array Controller HSOF Version 7.3 Configuration
Manual for details."
Indicates that a portion of an example or figure has
. been omitted, for example:
. A D D RAIDSET RAID1 DISK10000 DISK20000
I N I T I A L I Z E RAID1
S H O W RAID1
"this controller" The controller serving your current CLI session
through a local or remote terminal.
"other controller" The controller in a dual-redundant pair that's
connected to the controller serving your current
CLI session.
Special Notices
This book does not contain detailed descriptions of standard safety
procedures. However, it does contain warnings for procedures that
could cause personal injury and cautions for procedures that could
xiv Service Manual
damage the controller or its related components. Look for these
symbols when you're carrying out the procedures in this book:
Warning A warning indicates the presence of a hazard that can cause
personal injury if you do not avoid the hazard.
Caution A caution indicates the presence of a hazard that might
damage hardware, corrupt software, or cause a loss of data.
In addition, there are two other notices to aid you in your understanding
of the subject mater being read:
Tip A tip provides alternative methods or procedures that may not be
immediately obvious. A tip may also alert prior customers that the
controller behavior being discussed is different from prior software or
hardware versions.
Note A note provides additional information that's important to the
completion of an instruction or procedure.
Required Tools
The following tools are needed for servicing the controller, cache
module, and external cache battery:
s A small screwdriver for loosening and tightening the cable-
retaining screws.
s An antistatic wrist strap.
s An antistatic mat on which to place modules during servicing.
s An SBB Extractor for removing StorageWorks building blocks.
This tool is not required, but it will enable you to provide more
efficient service.
Preface xv
Related Publications
The following table lists some of the documents related to the use of
the controller, cache module, and external cache battery.
Document Title Part Number
HSZ70 Array Controller HSOF Version 7.3 EKCLI70RM. A01
CLI Reference Manual
HSZ70 Array Controller HSOF Version 7.3 EKHSZ70CG. A01
Configuration Manual
HSZ70 Array Controller HSOF Version 7.3 EKHSZ70SV. A01
Service Manual
SPD xx.xx. 00
HSZ70 Family Array Controller Operating
Software (HSOF) Version 7.3 Software
Product Description
Getting StartedHSZ70 Solutions Software AAR60KDTE
Version 7.3 for DIGITAL UNIX
Getting StartedHSZ70 Solutions Software AAR8A7DTE
Version 7.3 for OpenVMS
Polycenter Console Manager See the Getting
Started guide for the
platform-specific
order number
StorageWorks Array Controller HSZ70 Array EKHSZ70RN. B01
Controller Operating Software HSOF Version
7.3 Release Notes
StorageWorks Getting Started with Command AAR0HJCTE
Console, Version 2.1
EKSW600UG
DIGITAL StorageWorks Ultra SCSI RAID
Cabinet Subsystem (SW600) Installation and
User's Guide
DIGITAL StorageWorks Ultra SCSI RAID EKBA370UG
Enclosure (BA370-Series) User's Guide
The RAIDBOOK--A Source for RAID RAID Advisory
Technology Board
xvi Service Manual
Revision History
The current revisions of this document include:
EK-HSC70-SV.B01 HSOF V7.3 January 1999
EK-HSC70-SV.A01 HSOF V7.0 July 1997
11
1
CHAPTER
General Description
This chapter describes in general terms, the HSZ70 Array Controller
and the modules that support its operation. The following lists the
contents of this chapter:
s "Subsystem Typical Installation" on page 1-1
s "Controller Physical Description" on page 1-3
"Architecture" on page 1-5
"HSOF Software" on page 1-11
s "Cache Module" on page 1-18
s "External Cache Battery," page 1-19
s "Array Controllers and Hot Swapping," page 1-21
s "Host Cabling" on page 1-22
Subsystem Typical Installation
Figure 11 shows an example subsystem using a DS-BA370 rack-
mountable enclosure:
s HSZ70 controller--Quantity 1 or 2; each supported by a cache
module.
s External cache battery (ECB)--Quantity 1 or 2; provides backup
power to the cache module in the event of a power failure.
s Environmental monitoring unit (EMU)--monitors the conditions
within the storage subsystem and alerts the controller of potential
dangers or failures that could be caused by an abnormal
environment (see your associated subsystem enclosure manual for
more information on the EMU).
s Power verification and addressing module (PVA)--provides a
unique address for each enclosure in an extended (more than one
enclosure) subsystem.
12 Service Manual
Figure 11 Typical Installation of an HSZ70
13
12
1
11
2
10
3
9 4
8
5
6
7
CXO6702A
Table 11 Key to Figure 11
Item Description Part No.
1 BA370 rack-mountable enclosure DSBA370AA
2 Power cable kit (white) 17-03718-09
3 Cooling fans; 8 (2 per shelf) DSBA35XMK
4 I/O module; 6 DSBA35XMN
DSBA35XEC
5 PVA module (provides a unique address
to each enclosure in an extended
subsystem).
General Description 13
Table 11 Key to Figure 11 (Continued)
Item Description Part No.
6 AC input module DSBA35XHE
7 Cache module; 1 or 2 70-33256-01
8 SC5650HSZ70 array controller; 1 or 2 DS-HSZ70-AH
DSBA35XEB
9 Environmental monitoring unit (EMU)
The EMU monitors the subsystem
environment alerting the controller of
equipment failures that could cause an
abnormal environment.
10 180-watt power supply; 8 (2 per shelf) DSBA35XHH
11 Power cable kit (black) 17-03718-10
s External cache battery (ECB), single DSHS35XBC
12
s External cache battery (ECB), dual DSHS35XBD
(two ECBs in one Storage Building
Block (SBB), which provide backup
power to the cache modules during a
primary power failure.
13 Subsystem Building Block (SBB) - a tape See release notes
or disk drive unit inside a standard case . for qualified disk/
tape drive numbers
Controller Physical Description
The HSZ70 controller provides its host processor with high
performance, high-availability access to SCSI2 storage devices. See
the product-specific release notes that accompanied the HSOF software
release for the most recent list of supported devices and operating
systems.
Take a few moments to familiarize yourself with the controller physical
layout as shown in Figure 12.
14 Service Manual
Figure 12 HSZ70 Physical Layout
1
7
2
5
4 6
3
CXO5503D
Table 12 Key to Figure 12
I t em Des cription
Operator Control Panel (OCP)
Reset Button
Local Connection Port
Host Port Cable Slot
Program Card Slot
Module Locking/Release Levers (2)
Program Card Eject Button
From the perspective of the host, the controller is a SCSI-2 device
connected to one of its I/O buses. Consequently, the host sends I/O
requests to the controller as it would to any SCSI-2 device.
From the subsystem perspective, the controller receives the I/O
requests and directs them to the devices in the subsystem. Because the
controller processes the I/O requests, the host is not burdened by the
processing that's typically associated with reading and writing data to
multiple storage devices.
The controller also provides the ability to combine several disk drives
into a single, high performance storage unit called a storageset.
Storagesets are implementations of RAID technology (Redundant
Array of Independent Disks). This technology ensure that every
General Description 15
unpartitioned storageset, whether it uses two disk drives or ten, appears
as a single storage unit to the host. See the HSZ70 Array Controller
HSOF Version 7.3 Configuration Manual for more information about
storagesets and how to configure them.
The components accessed by the user are conveniently located on the
front panel, such as the local connection port and the operator control
panel (OCP). The host port and program card slot are also located on
the front panel, making it easy to update the HSOF software or to
connect the controller to a different host.
Architecture
The HSZ70 controller architecture includes the components shown in
the block diagram in Figure 13. Each of the components are described
in the paragraphs that follow.
Policy Processor
The policy processor is an Intel 80960CF i960 microprocessor and
coordinates, controls, and executes the HSOF software for the
controller. The i960 executes the software contained on the Program
Card and provides an instruction execution rate of 25MHz from its
internal clock. The i960 controls all but low-level device and host-port
operations.
The i960 internal cache is augmented by a separate 32KB instruction/
data (I/D) cache. This static RAM cache provides the i960 nearly
immediate access to the instructions and variables that it needs to
operate.
Program Card
The HSOF software is stored on a 2MB PCMCIA program card. The
policy processor loads the software from the program card to the local
memory during controller initialization.
Note The PCMCIA card must remain inserted at all times. The
HSZ70 Controller will not operate without this card in place.
16 Service Manual
Figure 13 HSZ70 Architecture
PCMCIA card
2 MB with Local-
Policy NVMEM Timer Diagnostic
Dual
program connection
OCP
processor HW registers
UART
capability 32 KB port
IBUS
To other controller's cache module
Local and MDAL bus CDAL bus
Bus
buffer
To cache module
exchanger
memory
16MB
NBUS
Host port Device ports (6)
Value-added
functions
SCSI host port SCSI device port
processor processor
Wide Ultra SCSI
differential
transceivers
16 bit
CXO5569A
Nonvolatile Memory
The controller has 32KB of nonvolatile memory (NVMEM) with which
to store the following data:
s Controller configuration parameters (such as its SCSI target IDs,
preferred IDs, prompt text, transfer rate, and failover status).
s Subsystem configuration, such as:
Name and location of disk drives.
Manner in which disk drives are combined into storagesets (or
used in the spareset).
Unit numbers assigned to the storagesets.
s Previous four "last failure" and "memory-system failure" entries
received from the fault manager.
General Description 17
NVMEM is preserved by an internal battery that provides power in the
event of a power failure.
Dual UART
The dual UART (Universal Asynchronous Receiver/Transmitter)
provides two functions to the HSZ70:
s Supports serial communication for a local connection to the
Maintenance Port.
s Provides a serial communication link between the two controllers
in a dual-redundant configuration.
The UART allows the two controllers to communicate independently of
the CDAL buses. The UART is the failover communication port,
informing the other controller of its present state and configuration.
Timer
The i960 processor controls and interrupts the timer at programmed
intervals to track timeouts, interrupts, LED flashing frequencies, and so
forth.
Diagnostic Registers
The controller has two write and two read diagnostic registers.
Diagnostic and functional software use the write diagnostic registers to
control the devices and the controller. For example, some bits in the
registers activate test modes for forcing errors in the controller; other
bits control the operator control panel LEDs. The policy processor uses
the read diagnostic registers to determine the cause of an interrupt when
one occurs.
Operator Control Panel
The operator control panel (OCP; see Figure 14) contains a reset
button, six port quiesce buttons, and six LEDs:
s The Reset button () normally flashes at a once per second rate
indicating that the controller is functioning properly.
s The Port quiesce buttons () are used to turn off the I/O activity on
the controller device ports. To quiesce a port, push its port button
and hold until the corresponding port LED remains lit. Push the
port button again to resume I/O activity on the port.
18 Service Manual
s The six LEDs () correspond to the six controller device ports and
remain off during normal operation. If an error occurs, the reset
button and LEDs illuminate in a solid or flashing pattern to help
you diagnose the problem (see Appendix A, "Operator Control
Panel LED Description" for the list of codes and patterns).
Figure 14 OCP
1 2
1 2 3 4 5 6
HSZ70
4
5 3
CXO6547A
In addition, there are two international symbols placed on the front of
the OCP:
s The SCSI standard symbol for differential SCSI bus () identifies
the HSZ70 Array Controller as a SCSI-2 differential device to the
host.
s The ISO 7000 Standard for "reset" or "initialization" () is placed
just below the controller reset button.
Maintenance Connection Port
The maintenance connection port provides the location to connect a
maintenance terminal, laptop, or PC to the controller so that you can
upgrade the software, configure or troubleshoot the controller. This port
accepts a standard RS-232 jack from any EIA-423 compatible terminal
or a PC with a terminal-emulation program. The port supports serial
communications up to 19200 baud using 8 data bits, 1 stop bit, and no
parity (see the HSZ70 Array Controller HSOF Version 7.3
Configuration Manual, "Establishing a Local Connection to the
Controller" on page 4-2).
General Description 19
Local Memory
The local memory loads and stores the HSOF software from the
program card each time the controller initializes. As a result, the local
memory contains instructions for the i960, the software variables, and
the data structures (which include the i960 look-up table). This single-
point of storage ensures that the data structures and buffers remain
consistent during the controller operation.
The local memory consists of:
s Dynamic RAM controller
s Arbitration engine
s Gate array controller
s 16MB of dynamic RAM
Parity-protected 9-bit error detection and correction code improves
error detection and data recovery. All controller buses have access to
the local memory through the bus exchanger and the MDAL bus.
Buses
The HSZ70 controller architecture includes the following buses:
s IBUS--I960 bus; conveys data to and from the i960 processor and
the other components on the IBUS. The bus conveys code and text
from the program card, code and data from the i960 I/D cache, and
configuration information to the NVMEM.
s MDAL--Memory Data and Address Lines; conveys memory data
and address information to and from the local buffer memory that
originate from the IBUS or NBUS.
s CDAL--Cache Data and Address Lines; conveys cache data and
address information to and from either cache module. Addresses
may originate from the IBUS or NBUS of either controller in a
dual-redundant configuration. The CDAL conveys information to
the surviving controller in the event of a failover.
s NBUS--conveys data to and from any of the components on the
NBUS (for example, host ports, device ports, and the value-added
functions chip). These components may access each other, the local
buffer memory, and either cache module.
Bus Exchanger
The bus exchanger facilitates high-speed communication between local
memory and the devices on the IBUS, MDAL bus, CDAL bus, and
110 Service Manual
NBUS. The bus exchanger operates as a four-way cross-point switch
that coordinates addresses and data between any two ports on the
exchanger.
Value-Added Functions Chip
This chip generates the RAID 5 parity on the first write of the data.
Upon detection of a RAIDset failure, this chip regenerates the parity to
recover the data that was stored on a failed RAIDset member. This
action is accomplished by performing an XOR of the parity data on the
surviving RAIDset members. The value-added functions circuit acts as
an accelerator for this RAID XOR operation as well as assisting with
device compare operations.
This chip is also programmed to conduct large-block read and writes
from failed controller cache module to the surviving controller cache
module in event of a failover.
Host Port
The host port is made up of an:
s NCR 53C770 Wide Ultra-SCSI processor,
s Wide Ultra-SCSI differential transceiver, and
s VHDCI SCSI connector.
The controller connects to a host bus through a SCSI-2 trilink
connector attached to the VHDCI SCSI connector. If the controller is at
the end of the host bus, an external terminator is required.
The Wide Ultra-SCSI processor reads and executes scripts from the
local memory to perform command and DMA operations. The policy
processor sets and maintains the operation of the Wide Ultra-SCSI
processor.
Device Ports
The controller communicates with the devices and modules in the
subsystem through three backplane connectors. Each connector
contains two ports to give the controller access to the six SCSI2
single-ended buses available in the enclosure. Each device port is made
up of an NCR 53C770 Wide Ultra-SCSI processor to support Wide
Ultra, single-ended SCSI communication to the devices in the
General Description 111
subsystem. Like the host port, the policy processor sets and maintains
the operation of the Wide Ultra processor.
Based on SCSI-2 standards, each bus connected to a device port can
support up to 16 IDs (targets plus initiators). However, the practical
considerations of StorageWorks packaging limit the use to 12 target IDs
and two initiator IDs per bus.
HSOF Software
The HSOF software (loaded into local memory when the controller
initializes), provides the following functions:
s Initialization Diagnostics
s Executive Functions
s Host Interconnect Functions
s User-Interface Functions
s Subsystem Management Functions
s Device Services
s Value-Added Functions
Each of these are described in the following paragraphs.
Initialization Diagnostics
When the controller initializes, it performs the following "gono go"
tests to detect hardware and software faults:
s Policy Processor Built-In Self-Test
s Core Module Integrity Self-Test
s DAEMON Tests
These tests verify the integrity of the controller architecture as well as
many of the components that support the controller in its enclosure.
Figure 15 contains a block diagram of the initialization diagnostics.
112 Service Manual
Figure 15 Initialization Diagnostics
i960 BIST
Policy processor
Core MIST
Read/write diagnostic register
Program card contents
Timer
DUART
DRAB/DRAM
Bus parity
Registers
Journal SRAM
I/D cache
Apply patches
EXEC
MIST DAEMON
Device ports Selftest
Host port loop
Cache module
Value-added functions
Functional code
CXO3697C
Policy Processor Built-In Self-Test
The controller begins the initialization process by executing its internal
built-in self-test (BIST; an integral test of the i960 processor):
s BIST fail--the controller reset button will be lit continuously (port
LEDs off).
s BIST pass--the RESET button flashes at an approximate once per
second rate.
General Description 113
Tip One of the more common causes of a BIST failure is a faulty or
improperly seated program card.
Core Module Integrity Self-Test
When BIST completes successfully, the controller reads the initial boot
record (IBR) to determine the address of the hardware setup parameters
and process control information. The software on the program card is
then initialized to the IBR parameters. The initialization routines and
diagnostics now begin to test the controller module itself. These tests
(part of the HSOF software) are collectively known as the core module
integrity self-tests (core MIST).
If a fault occurs during core MIST, the OCP displays an LED code
("Operator Control Panel LED Description," page A1) and the register
contents may be displayed on the local terminal.
Core MIST performs the following functions in order:
1. Sets the initial state of the read/write diagnostic register.
2. Validates the contents of the program card by reading each memory
location, computing an error detection code (EDC), then comparing the
EDCs against preset EDCs.
3. Checks the controller internal buses and components attached to them:
IBUS parity, I/D cache, diagnostic registers, DUART, the local memory,
and so on.
To check these components, the core MIST:
s Selects a device, then checks whether the bus selected that device.
s Verifies legal transfer sizes work and illegal transfer sizes don't.
s Writes to and reads back from all legal addresses.
s Checks write/read boundaries by attempting to access nonexistent
addresses.
4. Loads the software into the first two megabytes of local memory. Core
MIST uses the EDC compare method to validate the memory contents
with the program card to confirm a successful download.
5. Applies memory-resident code patches and updates the free memory list
accordingly.
6. Initializes the i960 microprocessor with the IBR parameters.
7. Passes control to EXEC when the core MIST tests are complete.
114 Service Manual
DAEMON Tests
The Executive functions (EXEC) calls the diagnostic and execution
monitor (DAEMON) to test the:
s Device ports.
s Host port.
s Cache module.
s Value-added software functions.
Tip You may re-run the controller DAEMON tests (also called the
self-test loop as shown in Figure 13) as a troubleshooting aid. See
"Self Test Run Procedure" on page 2-33.
s To test the host and device ports, DAEMON checks each NCR
53C770 microprocessor:
DAEMON passes the hardware if one device port is OK.
DAEMON fails the hardware if:
* All device ports fail, or
* The DUART fails the core MIST and the host port fails the
DAEMON test.
s To test the cache module, DAEMON checks for unwritten data:
No data exists. DAEMON tests the DRAB memory controller
and the ECB batteries. If they pass, DAEMON passes control
to the functional code. The cache manager continues to test the
cache memory.
Note At least the first megabyte of the memory must test OK,
or the cache module is failed.
Unwritten data exists--DAEMON tests only the batteries, and
postpones other tests. The cache manager flushes the unwritten
data after testing the DRAB and memory.
If cache is locked by the other controller in dual-redundant
configurations, then all cache DAEMON diagnostics are
postponed. During functional code, when the cache manager
determines that the cache is unlocked, the cache manager tests the
DRAB, batteries, and memory.
General Description 115
DAEMON handles all interrupts and errors received during cache
module testing. If DAEMON receives an interrupt, it stops
initializationand displays the error as an LED code on the OCP.
s Finally, to ensure RAIDset functionality, DAEMON tests the XOR
operations of the value-added hardware and its associated buffer
memory. Initialization stops if the XOR operation test fails.
Executive Functions
The executive functions (EXEC) controls the interrupts, thread,
queuing support, timers, and so forth to ensure a non-preemptive
interrupt-driven environment.
Host Interconnect Functions
The host interconnect functions support the SCSI2 protocol with the
following features:
s SCSI passthrough software to the CLI.
s Tagged-command queuing on the host and device side.
s Mode select/sense support for SCSI.
User-Interface Functions
The command line interpreter (CLI) provides a direct, command line
interface to the controller. Issue CLI commands via a local terminal
connected to the controller maintenance port or the host via HSZterm.
The CLI provides two kinds of commands:
s SET/SHOW commands for setting and showing the controller ID,
name, path controls, and other configuration information.
s ADD/DELETE commands for adding and deleting devices,
storagesets, and logical units.
See the HSZ70 Array Controller HSOF Version 7.3 CLI Reference
Manual for detailed information about each of the CLI commands. See
the System Manager's Guide for HSZterm for more information about
installing and using HSZterm.
Subsystem Management Functions
The HSOF software contains the following utilities for managing the
subsystem:
s Fault Management Utility (FMU)
116 Service Manual
s Virtual Terminal Display (VTDPY)
s Disk Inline Exerciser (DILX)
s Field Replacement Utility (FRUTIL)
s Configuration Utility (CONFIG)
s HSUTIL
s Code Load/Code Patch Utility (CLCP)
s Configuration menu (CFMENU)
s Clone
Each of these is described in the following paragraphs.
Fault Management Utility (FMU)
Use the FMU to control the display of spontaneous events and failure
messages that the fault management software reports to the local
terminal. See "Checking Failure Entries," page 2-10 for information on
how to use FMU.
Virtual Terminal Display (VTDPY)
Use VTDPY to display performance data about the controller and other
subsystem components. Use VTDPY to investigate processor
utilization, host port activity and status, device state, logical unit state,
and cache and I/O performance. See "VTDPY Run Procedures" on
page 2-17 for more information.
Disk Inline Exerciser (DILX)
Use DILX to test and verify operation of the controller and its attached
SCSI-2 disk drives. DILX generates intense read/write loads to selected
disk drives while monitoring their performance and status. See "DILX
Run Procedure" on page 2-29, for more information about this
exerciser.
Field Replacement Utility (FRUTIL)
Use FRUTIL to assist in the replacement of a failed controller (in a
dual-redundant configuration) without shutting down the subsystem.
You can also use this menu-driven utility to replace cache modules and
external cache batteries. Most of the procedures beginning on page
3-13, "Dual-Redundant Controller Configuration", explain how to use
FRUTIL.
General Description 117
Configuration Utility (CONFIG)
Use CONFIG to add one or more storage devices to the subsystem. See
the HSZ70 Array Controller HSOF Version 7.3 Configuration Manual
for more information about using the CONFIG utility.
HSUTIL
Use this utility program to upgrade the firmware on the disk or tape
drives on the subsystem. See "Upgrading Device Firmware" on page
4-9 for more information about this utility.
Code Load/Code Patch Utility (CLCP)
Use the CLCP utility to upgrade or patch controller software. See
"Firmware Upgrade Procedure," page 4-10 for more information on
how to use this utility.
Configuration menu (CFMENU)
Use CFMENU to configure the storagesets in the subsystem. See the
HSZ70 Array Controller HSOF Version 7.3 Configuration Manual for
more information about using CFMENU.
Clone
Use the Clone utility to duplicate the data on any unpartitioned single
disk unit, stripeset, or mirrorset. You can then backup the cloned data
while the original storageset remains online. See the HSZ70 Array
Controller HSOF Version 7.3 Configuration Manual for more
information about using the clone utility.
Device Services
The SCSI2 device service software provides the following functions:
s Device port drivers
s Addressing, access, and tagged-command queuing for qualified
SCSI-2 devices
s Device warm swap
s Shelf and SBB observation and control
s Device error recovery
118 Service Manual
Value-Added Functions
The HSOF software provides the following value-added functions to
enhance the availability, performance, subsystem management, and
connectivity features of the controller:
s RAID functions to support the creation and operation of RAIDsets,
stripesets, mirrorsets, striped mirrorsets, and host-based volume
shadowing. See the HSZ70 Array Controller HSOF Version 7.3
Configuration Manual for more information about storagesets.
s Failover functions to support dual-redundant and multiple-bus
failover configurations. In either of these configurations, two
controllers exchange status signals and configuration information.
If one controller fails, the surviving controller takes over the failed
controller's devices and units. See the HSZ70 Array Controller
HSOF Version 7.3 Configuration Manual for more information
about these redundant configurations.
s Cache manager functions that control the caching of up to 128MB
of data to enhance the subsystem throughput.
Cache Module
Figure 16 shows a cache module with its ECB "Y" cable inserted.
Figure 11 shows its placement in the subsystem; Figure 17 shows the
ECB.
Figure 16 Cache Module and ECB "Y" Cable
5
4
1
~
2
3 2x
CXO5714A
General Description 119
Table 13 Key to Figure 16
Item Description Part No.
Cache-memory power LED N/A
ECB "Y" cable (to ECB) 70-33268-01
Retaining/Locking lever (2) N/A
Backplane connector N/A
s SIMM (2 or 4)
54-23391-01
s SIMM 64 MB pack DS-HSSIM-AB
The cache module increases the controller I/O performance by caching
read and write data.
s Read data--the controller can often satisfy a host read request
immediately from the cached data rather than having to access one
or more disk drives to obtain the data.
s Write data--the controller avoids the latencies associated with
writing data to a disk drive.
To further ensure the availability of write data, mirror two cache
| 16-25105-18
17-03718-09
17-03718-10
54-23391-01
70-33256-01
70-33268-01
DS-BN37A-02
DS-BN37A-03
DS-BN37A-05
DS-BN37A-0E
DS-BN37A-10
DS-BN37A-15
DS-BN37A-1E
DS-BN37A-20
DS-BN37A-25
DS-BN37A-2E
DS-HS35X-BC
DS-HS35X-BD
DS-HSSIM-AB
DS-HSZ70-AH
EK-HSC70-SV
|
