Compaq Computer Corporation
Houston, Texas
Configuration 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 US 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.
iii
Contents
Contents
Preface
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Electrostatic Discharge Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
VHDCI Cable Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Local-Connection Maintenance Port Precautions . . . . . . . . . . . . . . . . . . . xiv
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv
Special Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Required Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Chapter 1 Subsystem Introduction
Typical Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Summary of HSZ70 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
HSZ70 Basic Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Device-Side Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Host-Side Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Storagesets and Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Physically Connecting the Host to the Storage Array . . . . . . . . . . . . . . . .18
Logically Connecting the Storage Array to the Host . . . . . . . . . . . . . . . . .19
Mapping the Physical Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Mapping the Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Controller Key Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114
Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
iv Configuration Manual
Maintenance Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Controller Utilities and Exercisers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Fault Management Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Virtual Terminal Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Disk Inline Exerciser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
HSUTIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Code Load and Code Patch Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Clone Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Change Volume Serial Number Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Device Statistics Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Field Replacement Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Cache Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
External Cache Battery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Charging Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Chapter 2 Planning a Subsystem
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Controller Designations A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Controller Designations "This" and "Other" . . . . . . . . . . . . . . . . . . . . . . 22
Selecting a Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Transparent Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Multiple-Bus Failover Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuration Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Selecting a Cache Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
service manualRead Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Read-Ahead Caching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Write-Through Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Write-Back Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fault-Tolerance for Write-Back Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Non-Volatile Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Mirrored Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Dynamic Caching Techniques. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Cache Policies as a Result of Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Contents v
Assigning Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215
Assigning Logical Unit Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217
Command Console LUN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Host Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
Restricting Host Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220
Chapter 3 Planning Storage
Determining Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Choosing a Container Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Creating a Storageset Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Stripeset Planning Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Mirrorset Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
RAIDset Planning Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313
Striped Mirrorset Planning Considerations . . . . . . . . . . . . . . . . . . . . . . .316
Partition Planning Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .317
Defining a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .318
Guidelines for Partitioning Storagesets and Disk Drives. . . . . . . . . . . . .319
Choosing Switches for Storagesets and Devices. . . . . . . . . . . . . . . . . . . . . . .319
Enabling Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
Changing Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
RAIDset Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320
Replacement Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321
Reconstruction Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321
Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321
Mirrorset Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322
Replacement Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322
Copy Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322
Read Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323
Partition Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323
Device Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323
Transportability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323
Device Transfer Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325
Initialize Command Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325
Chunk Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .326
vi Configuration Manual
Save Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Destroy/Nodestroy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
ADD UNIT Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Access Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Maximum Cache Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Preferred Path. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Read Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Write Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Write-back Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Storage Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Creating a Storage Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Example Storage Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Using the LOCATE Command to Find Devices . . . . . . . . . . . . . . . . . . . 338
Moving Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
HSZ70 Array Controllers and Asynchronous Drive Hot Swap . . . . . . . 339
Container Moving Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
The Next Step... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Chapter 4 Subsystem Configuration Procedures
Establishing a Local Connection to the Controller. . . . . . . . . . . . . . . . . . . . . . 42
Local Connection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuration Procedure Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring a Single Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Cabling a Single Controller to the Host . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Single Controller CLI Configuration Procedure . . . . . . . . . . . . . . . . . . . . 48
Configuring for Transparent Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Cabling Controllers in Transparent Failover Mode . . . . . . . . . . . . . . . . 410
Transparent Failover Mode CLI Configuration Procedure . . . . . . . . . . . 411
Configuring for Multiple-Bus Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . 414
Cabling Controllers for Multiple-Bus Failover Mode. . . . . . . . . . . . . . . 414
Multiple-Bus Failover Mode CLI Configuration Procedure. . . . . . . . . . 415
Configuring Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Contents vii
Configuring a Stripeset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .419
Configuring a Mirrorset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .420
Configuring a RAIDset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .421
Configuring a Striped Mirrorset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .422
Configuring a Single Disk Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .422
Configuring a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423
Partitioning a Storageset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .423
Partitioning a Single Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .424
Assigning Unit Numbers and Unit Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . .425
Assigning a Unit Number to a Partition. . . . . . . . . . . . . . . . . . . . . . . . . .425
Assigning a Unit Number to a Storageset . . . . . . . . . . . . . . . . . . . . . . . .425
Assigning a Unit Number to a Single (JBOD) Disk . . . . . . . . . . . . . . . .426
Preferring Units in Multiple-Bus Failover Mode . . . . . . . . . . . . . . . . . . . . . .426
Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426
Changing the CLI Prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .426
Setting Maximum Data Transfer Rate . . . . . . . . . . . . . . . . . . . . . . . . . . .427
Set-Up Cache UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427
Adding Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .427
Adding One Disk Drive at a Time . . . . . . . . . . . . . . . . . . . . . . . . . .428
Adding Several Disk Drives at a Time . . . . . . . . . . . . . . . . . . . . . . .428
Adding/Deleting a Disk Drive to the Spareset . . . . . . . . . . . . . . . . .428
Enabling/Disabling Autospare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .429
Deleting a Storageset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .430
Changing Switches for a Storageset or Device . . . . . . . . . . . . . . . . . . . .431
Displaying the Current Switches . . . . . . . . . . . . . . . . . . . . . . . . . . .431
Changing RAIDset and Mirrorset Switches . . . . . . . . . . . . . . . . . . .432
Changing Device Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432
Changing Initialize Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432
Changing Unit Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .432
Chapter 5 Periodic Procedures
Formatting Disk Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Using the HSUTIL Utility Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Clone Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
viii Configuration Manual
Cloning a Single-Disk Unit, Stripeset, or Mirrorset . . . . . . . . . . . . . . . . . 55
Backing Up Your Subsystem Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Saving Subsystem Configuration Information to a Single Disk . . . . . . . . 58
Saving Subsystem Configuration Information to Multiple Disks . . . . . . . 58
Saving Subsystem Configuration Information to a Storageset . . . . . . . . . 59
Displaying the Status of the Save Configuration Feature . . . . . . . . . 59
Shutting Down Your Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Restarting Your Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Appendix A Controller Specifications
Physical and Electrical Specifications for the Controller. . . . . . . . . . . . . . . . .A2
Environmental Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A2
Appendix B System Profiles
Device Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B3
Device Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B4
Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B5
Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B6
Storage Map Template for PVA0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B7
Storage Map Template for PVA0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B8
Storage Map Template for PVA 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B9
Storage Map Template for PVA 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B10
Storage Map Template for PVA 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B11
Storage Map Template for PVA 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B12
Glossary
Index
ix
Figures
Figure 11 Subsystem Building Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Figure 12 Host and Storage Subsystem Bridge . . . . . . . . . . . . . . . . . . . .15
Figure 13 Example Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Figure 14 Subsystem Bus Block Diagram . . . . . . . . . . . . . . . . . . . . . . . .19
Figure 15 Physical Storage Device Interface . . . . . . . . . . . . . . . . . . . . 111
Figure 16 Example Host View of Target Addressing . . . . . . . . . . . . . 113
Figure 17 Key Controller Components . . . . . . . . . . . . . . . . . . . . . . . . .114
Figure 18 Location of Controllers and Cache Modules . . . . . . . . . . . .115
Figure 19 Operator Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
Figure 110 Cache Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
Figure 111 ECB for Dual-Redundant Controller Configurations . . . . .122
Figure 21 Location of Controllers and Cache Modules . . . . . . . . . . . . .22
Figure 22 "This" Controller and "Other" Controller . . . . . . . . . . . . . . . 23
Figure 23 Mirrored Caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210
Figure 24 Transparent Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . . .216
Figure 25 Multiple-Bus Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . .217
Figure 31 An Example Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 32 Example 3-Member Stripeset . . . . . . . . . . . . . . . . . . . . . . . . .36
Figure 33 Stripeset Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Figure 34 Distribute Members Across Device Ports . . . . . . . . . . . . . . . 39
Figure 35 Mirrorsets Maintain Two Copies of the Same Data . . . . . . .310
Figure 36 Mirrorset Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310
Figure 37 First Mirrorset Members Placed on Different Buses . . . . . .312
Figure 38 Parity Ensures Availability; Striping for Performance . . . . .313
Figure 39 RAIDset Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Figure 310 Striping and Mirroring in the Same Storageset . . . . . . . . . . .316
Figure 311 Striped Mirrorset Example 2 . . . . . . . . . . . . . . . . . . . . . . . . 317
Figure 312 Partitioning a Single-Disk Unit . . . . . . . . . . . . . . . . . . . . . . .318
Figure 313 Chunk Size Larger than the Request Size . . . . . . . . . . . . . . .327
Figure 314 Chunk Size Smaller than the Request Size . . . . . . . . . . . . . .328
Figure 315 Example Blank Storage Map . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 316 Completed Example Storage Map . . . . . . . . . . . . . . . . . . . . 338
Figure 317 Moving a Container from one Subsystem to Another . . . . .340
Figure 41 Terminal to Maintenance Port Connection . . . . . . . . . . . . . . 43
Figure 42 Optional Maintenance Port Connection Cabling . . . . . . . . . . 43
x Configuration Manual
Figure 43 The Configuration Flow Process 46
Figure 44 Connecting a Single Controller to Its Host 47
Figure 45 Connecting Dual-Redundant Controllers to the Host 410
Figure 46 Connecting Multiple Bus Failover, Dual-Redundant Controllers
to the Host 415
Figure 51 CLONE Steps for Duplicating Unit Members 55
xi
Tables
Table 11 Key to Figure 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 12 Summary of Controller Features . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 13 Key to Figure 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Table 14 Cache Module Memory Configurations . . . . . . . . . . . . . . . . 120
Table 15 Key to Figure 110 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Table 16 ECB Capacity versus Battery Size. . . . . . . . . . . . . . . . . . . . . . 122
Table 17 Key to Figure 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Table 2 1 Cache Policies and Cache Module Status . . . . . . . . . . . . . . . . 211
Table 2 2 Cache Policies and ECB Status . . . . . . . . . . . . . . . . . . . . . . . .213
Table 23 Unit Numbering Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Table 3 1 A Comparison of Container Types . . . . . . . . . . . . . . . . . . . . . . .33
Table 32 Maximum Chunk Sizes for a RAIDset . . . . . . . . . . . . . . . . . . 329
Table 3 3 ADD UNIT Switches for New Containers . . . . . . . . . . . . . . .332
Table 41 Key to Figure 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Table 42 PC/Maintenance Terminal Selection . . . . . . . . . . . . . . . . . . . . . 44
Table A1 Controller Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A2
Table A2 StorageWorks Optimum Operating Environment . . . . . . . . . . A2
Table A3 StorageWorks Maximum Operating Environment (Range) . . . A3
Table A4 StorageWorks Maximum Nonoperating Environment (Range) A3
xiii
Preface
This book describes the features of the HSZ70 array controller and
configuration procedures for the controller and storagesets running
HSOF Version 7.3.
This book does not contain information about the operating
environments to which the controller may be connected, nor does it
contain 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 xiii
s VHDCI Cable Precautions, page xiv
s Local-Connection Maintenance Port Precautions, page xiv
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 you're
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. Make sure 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.
xiv Configuration 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 extraordinarily 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 port generates, uses, and radiates radio-frequency
energy through cables that are connected to it. This energy may
interfere with radio and television reception. Do not leave a cable
connected to this port when you're not communicating with the
controller.
xv
Conventions
This book adheres to the typographical conventions and special notices
found in the table and paragraphs that follow.
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 or
S E T THIS_CONTROLLER ID=(n,n,n,n,)
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.
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.
xvi Configuration Manual
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
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.
Tip A tip provides alternative methods or procedures that may not be
immediately obvious. A tip may also alert prior customers that the
controller's 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.
xvii
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. B01
CLI Reference Manual
HSZ70 Array Controller HSOF Version 7.3 EKHSZ70CG. B01
Configuration Manual
HSZ70 Array Controller HSOF Version 7.3 EKHSZ70SV. B01
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
EKHSZ70RN. B01
StorageWorks Array Controller HSZ70 Array
Controller Operating Software HSOF Version
7.3 Release Notes
StorageWorks Getting Started with Command AAR0HJCTE
Console, Version 2.1
EKSW600UG
StorageWorks Ultra SCSI RAID Cabinet
Subsystem (SW600) Installation and User's
Guide
StorageWorks Ultra SCSI RAID Enclosure EKBA370UG
(BA370-Series) User's Guide
The RAIDBOOK--A Source for RAID RAID Advisory
Technology Board
xviii Configuration Manual
Revision History
The current revisions of this document include:
EK-HSC70-CG.B01 HSOF V7.3 December 1998
EK-HSZ70-CG.A01 HSOF V7.0 July 1997
11
1
CHAPTER
Subsystem Introduction
This chapter of the HSZ70 Array Controller Configuration Manual
introduces the features and components of the HSZ70 controller:
s "Typical Installation," page 1-1
s "Summary of HSZ70 Features," page 1-3
s "Storagesets and Containers," page 1-7
s "Controller Key Components," page 1-14
s "Operator Control Panel," page 1-15
s "Maintenance Port," page 1-17
s "Controller Utilities and Exercisers," page 1-17
s "Cache Module," page 1-20
s "External Cache Battery," page 1-21
s "Charging Diagnostics," page 1-23
Typical Installation
Figure 11 shows the major components, or basic building blocks, of a
typical storage subsystem. Table 11 lists and describes these building
blocks.
12 Configuration Manual
Figure 11 Subsystem Building Blocks
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).
Subsystem Introduction 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 HSZ70 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
Summary of HSZ70 Features
Table 12 contains a summary of the HSZ70 Array Controller features.
Table 12 Summary of Controller Features
Feature Supported
Host protocol SCSI2
Host bus interconnect Wide Ultra Differential
SCSI2
Device protocol SCSI2
Device bus interconnect Fast Wide Ultra Single-
ended SCSI-2
14 Configuration Manual
Table 12 Summary of Controller Features (Continued)
Feature Supported
Number of SCSI device ports 6
Number of SCSI device targets per port 12
72
Maximum number of SCSI devices
(with two additional BA370 shelves)
RAID levels 0, 1, 0+1, 3/5
Cache size 64 or 128 MB
Mirrored write-back cache sizes 32 or 64 MB
Max number of host target IDs per controller 8
Program card updates Yes
Device warm swap Yes
Exercisers for testing disks Yes
Tape drives, loaders, and libraries Yes
Number of configuration entities 191
(devices + storagesets + partitions + units)
Maximum number of RAID 5 storagesets 20
Maximum number of RAID 5 and RAID 1
storagesets:
s Dual-controller configurations
30
s Single-controller configurations
20
Maximum number of RAID 5, RAID 1, and 45
RAID 0 storagesets
Maximum number of partitions per 8
storageset or disk drive
Maximum number of units presented to host 64
Maximum number of units presented to host 63
with StorageWorks Command Console
Maximum number of devices per unit 32
Maximum host port transfer speed 20 MHz
Largest device, storageset, or unit 512 GB
Subsystem Introduction 15
HSZ70 Basic Description
Your controller is the intelligent bridge between your host and the
devices in your storage subsystem.
The controller may be thought of as containing three main (but
distinct) parts. The array controller is best understood if these three
functional divisions are conceived as separate entities. The three
entities are:
s Device-side logic
s Intelligent bridge
s Host-side logic
The host-side logic and device-side logic sections both use SCSI-2
protocol. This means that the terms used to describe both interfaces are
the same: both have ports, targets, and LUNs. This terminology can
cause confusion between device-side and host-side functions. Keeping
this simple model in mind can help eliminate confusion.
The model is shown in Figure 12, and is explained in the following
sections.
Figure 12 Host and Storage Subsystem Bridge
Storage
Host
subsystem
Controller
CXO5505A
16 Configuration Manual
Device-Side Logic
The device side is the controller's interface to a collection of physical
storage devices (the device array). Each of these storage devices is
capable of SCSI-2 level communication and each functions
independently of the others. The controller connects to these devices
through six device-side SCSI buses.
The intelligent bridge performs the internal functions of the controller.
The intelligent bridge both separates and links the device-side and
host-side logic functions. These functions are defined as follows:
s Separate--The intelligent bridge is a barrier between the device-
side and host-side logic, making the device-side logic (and hence
the storage devices) completely invisible and inaccessible to the
host.
s Link--The intelligent bridge creates virtual disks that reference
(maps), the contents of the real, device-side disks in defined ways.
The bridge creates an illusion for the host: the host sees only the
virtual storage devices created by the intelligent bridge and knows
nothing at all about the physical storage devices that reside behind
the controller (device-side). These virtual storage devices look and
operate differently than the physical, device-side storage devices.
The virtual storage devices appear and act to the host as real storage
devices with normal operating parameters. The host performs SCSI
commands to these virtual storage devices set up by the controller.
When the host sends a command to one of the virtual storage devices,
the controller translates and executes the command on the physical
storage device that is mapped to the virtual.
Host-Side Logic
The host-side logic is the HSZ70 Array Controller interface to one or
more hosts. A host is a computer attached to one of the host-side SCSI
buses. The host can access the virtual disks created by the intelligent
bridge when attached to one of the host-side SCSI buses. The
controller is said to "present" these virtual storage devices to the host.
The host sees only what the intelligent bridge lets it see: a number of
high-capacity, high-availability, and/or high-reliability virtual storage
devices. The physical reality of what is there (an array controller and
an array of physical disk and/or tape drives), is completely masked.
Subsystem Introduction 17
See the product-specific release notes that accompanied the software
release for the most recent list of supported devices and operating
systems.
In addition to managing SCSI I/O requests, the controller provides the
ability to:
s Combine several disk drives into a single, high-performance
storage unit called a storageset.
s Partition the single disk drive or storageset.
Storagesets and Containers
Storagesets are implementations of RAID technology (Redundant
Array of Independent Disks). RAID technology ensures that every
unpartitioned storageset (regardless of the number of disk drives),
appears to the host as a single storage unit.
See Chapter 3, "Planning Storage," for more information about
storagesets and how to configure them.
The Storageset types used by the HSZ70 are shown in
Figure 13 "Example Containers" and described in the following list:
s RAID 0 (Stripesets)--disk drives combined in serial to increase
transfer or request rates.
s RAID 1 (Mirrorsets)--disk drives combined in parallel to provide
a highly-reliable storage unit.
s RAID 0+1 (Striped Mirrorsets)--combined mirrorsets in serial and
parallel providing the highest throughput and availability.
s RAID 3/5 (RAIDsets)--disk drives combined in serial (as RAID 0)
but also store parity data ensuring high reliability.
Storagesets are augmented by two other disk storage configurations:
s Single disk devices (also known as JBOD--just a bunch of disks).
This configuration is a single disk device not a part of any of the
RAID technology (storagesets). In this configuration, a single disk
may be a distinct unit number.
s Partitions--A configuration of single disk drives or a storageset
whose data storage area is partitioned.
18 Configuration Manual
Note Any of the storagesets shown may also be partitioned unless
you are operating with a dual-redundant controller configuration.
For a complete discussion of RAID, refer to The RAIDBOOK--A
Source Book for Disk Array Technology.
Figure 13 illustrates the concept of the installed disk drives being
configured as storagesets, individual storage devices, or partitions. The
collective term for these is "containers".
Figure 13 Example Containers
Containers
Partition
Betty making new one:
Stripeset Striped mirrorset RAIDset
Single Mirrorset
(R0) (R0+1) (R3/5)
devices (R1)
(JBOD)
Storagesets
CXO6677A
The controller also allows tape drives, loaders, and libraries to be
added your subsystem to meet your storage requirements.
Physically Connecting the Host to the Storage Array
The controller provides a host system physical access to a peripheral
device storage array by using host and device buses. Figure 14 shows
that the host and device bus interfaces are both Small Computer
System Interface (SCSI) buses.
Subsystem Introduction 19
Figure 14 Subsystem Bus Block Diagram
Host
Ultra SCSI bus
(Differential)
Host port
Controller
Device Device
port 1 port 6
SCSI SCSI
device device
Ultra SCSI bus
(single ended)
SCSI SCSI
device device
CXO4602A
Logically Connecting the Storage Array to the Host
The controller uses a two-level mapping process to logically connect
the host to the storage array:
s The controller maps the physical devices on its six device buses to
storage containers created by the user.
s The controller maps its internal containers to user-created logical
units that are directly accessible by the host.
110 Configuration Manual
Mapping the Physical Devices
Figure 15 shows a typical physical storage device interface for a one-
cabinet subsystem (or the first cabinet of an extended subsystem). Each
of the controller's six input/output device ports supports a SCSI-2 bus
connected to storage devices (the maximum number dependent upon
the cabinet configuration and the SCSI specifications).
This connection is hardwired through the port I/O modules and the
enclosure backplane wiring.
Controller port-target-LUN (PTL) addressing is the process by which
the controller selects storage space within the specific, physical,
storage device. This process consists of three steps:
s The controller I/O port selection. The controller selects one of the
six I/O ports of the controller.
s The controller SCSI-2 bus target selection. The controller selects
the device's target ID.
s The controller-device logical unit (LUN) selection. The controller
selects the desired LUN within the specific storage device. In the
current implementation, there is only one LUN on each storage
device, therefore that LUN address is always 0.
Note The exception to this rule occurs when certain multi-LUN tape
loaders are used (therefore they would have a LUN of 0 or 1).
Refer to Figure 15; the illustration depicts the PTL addressing for a
single cabinet full of disk drives. The numbers in each "cell" of the
storage cabinet reflect the PTL of that particular device. In a three-
cabinet configuration the controller SCSI-2 target IDs would be as
follows:
s 1st cabinet: 0, 1, 2, 3
s 2nd cabinet: 8, 9, 10, 11
s 3rd cabinet: 12, 13, 14, 15
Note SCSI Target IDs 4, 5, 6, and 7 are not used by the storage
devices. They are reserved for the two possible controllers (ID 7, ID 6)
while the other two are not used.
Subsystem Introduction 111
Figure 15 Physical Storage Device Interface
Device-side
target IDs
Power Power
supply Disk10300 Disk20300 Disk30300 Disk40300 Disk50300 Disk60300 supply
3
Power Power
Disk10200 Disk20200 Disk30200 Disk40200 Disk50200 Disk60200
supply supply
2
Cabinet
Power Power
1 supply Disk10100 Disk20100 Disk30100 Disk40100 Disk50100 Disk60100 supply
Power Power
0 supply Disk10000 Disk20000 Disk30000 Disk40000 Disk50000 Disk60000 supply
Device-side 1 2 3 4 5 6
port number
1 2 3 4 5 6
I/O ports
Controller
CXO6699A
The PTL addressing of the storage devices is handled internally by the
controller. The controller receives a Unit Number from the host when a
read or write operation is requested. The controller translates the Unit
Number into the physical PTL address to select the drive. The unit
number-to-PTL correlation comes from the user-entered CLI
commands:
s ADD DISK container-name SCSI PTL (assigns a container name
to the PTL address).
s ADD UNIT unit-number container-name (assigns a Unit Number
(LUN) to the container name).
112 Configuration Manual
For both of these commands see the HSZ70 Array Controller HSOF
Version 7.3 CLI Reference Manual for details.
Mapping the Containers
Each logical unit the controller makes available to the host is
associated with a Target ID on the host SCSI bus. Figure 16 shows the
host view of the logical storage units.
The controller offers up to eight SCSI Target IDs to the host bus. Each
SCSI Target ID can offer up to eight logical units (LUNs) to the host.
Each logical unit is separately addressable and has configurable
operating attributes based on the container type that it is a part of.
The controller software enables the user to configure the LUNs in a
variety of ways to optimize for specific performance and availability
needs. The details of the configuration of each logical storage unit are
transparent to the host. The host uses the performance and availability
benefits of each unit without any of the overhead associated with the
optimization process.
Note Host-side SCSI LUNs and device-side SCSI LUNS share the
same name but have no relationship to one another.
Each host on the storage subsystem, is connected to the SCSI-2 bus by
way of a host bus adapter. The HSZ70 controller (or dual-redundant
controller pair) also connects to this SCSI-2 bus through the controller
host ports.
The SET this_controller ID= command selects up to eight host target
IDs to one controller (or controller pair). Figure 16 shows an example
of a subsystem using host target IDs of 0, 1, 2, 3, 4, 5, 8, and 9 (from
the range of 0--15). In each of the storage disks shown in the
illustration, the logical storage unit number is also noted. These logical
unit numbers (LUNs) were assigned with the ADD UNIT unit-number
container-name command.
Note In a typical subsystem, one of the LUNs is reserved for the
StorageWorks Command Console (SWCC).
Subsystem Introduction 113
Figure 16 Example Host View of Target Addressing
Host
adapter
at ID6
SCSI bus
Host
~
~
adapter
at ID7 ID0 ID1 ID2 ID3 ID9
D0 D100 D200 D300 D900
D1 D101 D201 D301 D901
D2 D102 D202 D302 D902
D107
D7 D207 D307 D907
CXO6700A
114 Configuration Manual
Controller Key Components
The HSZ70 is made up of the key components shown in Figure 17.
Figure 17 Key Controller Components
1
7
2
5
4 6
3
CXO5503D
Table 13 Key to Figure 17
Item Description
Operator Control Panel (OCP)--A collection of amber-
colored LEDs that indicate status of the controller (see
"Operator Control Panel," page 1-15 and the HSZ70 Array
Controller HSOF Version 7.3 Service Manual for details).
Reset Button/Indicator--Performs a hard reset of the
controller when pushed. Its light indicates normal operation of
the controller when flashing at a once per second rate.
Maintenance Connection Port--A connection port for a
maintenance terminal or PC. This port allows communication
with the controller for setup and configuration.
Host Connection Port--A port for the connection of the host
CPU with the controller.
Program Card Slot--A place to insert the PCMCIA program
card. The card must be in place for normal operation. Each
time the controller reboots, the HSOF software is read from
the program card.
Program Card Eject Button--Ejects the PCMCIA program
card from the program card slot when pushed.
Locking Levers--Levers to lock the controller in the shelf.
Subsystem Introduction 115
Under normal circumstances, you will not need to remove the
controller from its cabinet. The components that you will use most
often are located on the front of the controller.
The enclosure backplane enables two controllers to communicate with
each other in dual-redundant configurations. It also contains the device
ports that enable the controller to communicate with the devices in the
subsystem.
Each controller is supported by its own cache module. Use Figure 18
in conjunction with Figure 11 to locate the installed position of the
cache module-to-controller support in a BA370 rack-mountable
enclosure.
Figure 18 Location of Controllers and Cache Modules
EMU PVA
Controller A
Controller B
Cache module A Cache module B
CXO6283A
Tip For single controller installations, it is recommended that you
use the slots for controller A and cache module A. Slot A responds to
SCSI target ID number 7; slot B responds to target ID number 6.
Operator Control Panel
The operator control panel (OCP; see Figure 19) 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.
116 Configuration 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 (Appendix A, "Operator Control Panel
LED Description").
Figure 19 Operator Control Panel
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 = SCSI Standard symbol for differential SCSI bus. This
identifies the HSZ70 Array Controller as a SCSI-2 differential
device to the host.
s = ISO 7000 Standard symbol for "reset" (or initialization ). This
symbol is placed just below the controller reset button.
See Figure 17 for the location of the OCP on the HSZ70 Array
Controller and the HSZ70 Array Controller HSOF Version 7.3 Service
Manual for an explanation of the LED codes that may appear on the
OCP.
Once installed, configured, and running, you should periodically check
the HSZ70 control panel. If an error should occur, one or more of the
LED lights on the control panel flashes in a pattern that will help you
diagnose the problem. Refer to the HSZ70 Array Controller HSOF
Version 7.3 Service Manual for details about troubleshooting your
controller.
Subsystem Introduction 117
Maintenance Port
You can access the controller to modify CLI commands (add a disk
drive, remove a disk drive, and so on) in two ways:
s Through a local terminal/PC via the maintenance port
s Through a remote terminal--sometimes called a virtual terminal or
host console--via the host.
It is recommended that you use a local terminal to carry out the
troubleshooting and servicing procedures in this manual. See
"Establishing a Local Connection to the Controller," page 4-2, for
more information about connecting the array controller with a
maintenance port cable.
Controller Utilities and Exercisers
The controller software includes the following utilities and exercisers
to assist in troubleshooting and maintaining the controller and the other
modules that support its operation:
s Fault Management Utility (FMU)
s Virtual Terminal Display (VTDPY)
s Disk Inline Exerciser (DILX)
s Configuration Utility (CONFIG)
s HSUTIL
s Code Load and Code Patch Utility (CLCP)
s Clone Utility (CLONE)
s Change Volume Serial Number Utility
s Device Statistics Utility
s Field Replacement Utility (FRUTIL)
Each of these is described in the paragraphs that follow.
Fault Management Utility
The Fault Management Utility (FMU) provides a limited interface to
the controller fault-management system. As a troubleshooting tool, you
can use the FMU to:
s Display the last-failure and memory-system-failure entries that the
fault-management software stores in controller nonvolatile
memory (NVMEM).
118 Configuration Manual
s Translate many of the event messages that are contained in the
entries related to the significant events and failures. For example,
entries may contain codes that indicate the cause of the event, the
software component that reported the event, the repair action, and
so on.
s Set the display characteristics of spontaneous events and failures
that the fault-management system sends to the local terminal or
host.
Virtual Terminal Display
Use the virtual terminal display (VTDPY) utility to aid in
troubleshooting the following issues:
s Communication between the controller and its hosts.
s Communication between the controller and the devices in the
subsystem.
s The state and I/O activity of the logical units, devices, and device
ports in the subsystem.
Disk Inline Exerciser
Use the disk inline exerciser (DILX) to investigate the data-transfer
capabilities of disk drives. DILX tests and verifies operation of the
controller and the SCSI2 disk drives attached to it. DILX generates
intense read and write loads to the disk drive while monitoring the
drive performance and status.
Configuration Utility
Use the configuration (CONFIG) utility to add one or more storage
devices to the subsystem. This utility checks the device ports for new
disk drives, then adds them to the controller configuration and
automatically names them.
HSUTIL
Use HSUTIL to upgrade the firmware on disk drives in the subsystem
and to format disk drives.
Subsystem Introduction 119
Code Load and Code Patch Utility
Use Code Load and Code Patch (CLCP) utility to upgrade or patch the
controller software and the EMU software. Whenever you install a new
controller, you must have the correct software version and patch
number.
Note Only field service personnel are authorized to upload EMU
microcode updates. Contact the Customer Service Center (CSC) for
directions in obtaining the appropriate EMU microcode and installation
guide.
Clone Utility
Use the Clone utility to duplicate the data on any unpartitioned
storageset or individual drive. Back up the cloned data while the actual
storageset remains online.
Note The clone utility may not be used with partitioned mirrorsets
or partitioned Stripesets.
Change Volume Serial Number Utility
The Change Volume Serial Number (CHVSN) utility generates a new
volume serial number (called VSN) for the specified device and writes
it on the media. It is a way to eliminate duplicate volume serial
numbers and to rename duplicates with different volume serial
numbers.
Note Only authorized service personnel may use this utility.
Device Statistics Utility
The Device Statistics (DSTAT) utility allows you to log I/O activity on
a controller over an extended period of time. Later, you can analyze
that log to determine where the bottlenecks are and how to tune the
controller for optimum performance.
120 Configuration Manual
Note Only authorized service personnel may use this utility.
| 12-43346-01
12-45238-01
12-45238-02
12-45238-03
16-25105-14
17-03511-01
17-03718-09
17-03718-10
17-04074-01
17-04074-04
70-33256-01
DS-HSZ70-AH
EK-HSC70-CG
EK-HSZ70-CG
XO-5135A-MC
XO-5172A-MC
XO-5316A-MC
|
