1. Manuals
  2. Brands
  3. Digital Equipment Manuals
  4. Controller
  5. StorageWorks HSZ70
  6. Configuration manual

Digital Equipment StorageWorks HSZ70 Configuration Manual

Array controller hsof version 7.0
Hide thumbs Also See for StorageWorks HSZ70:
Table of Contents

Advertisement

Quick Links

Download this manual
DIGITAL StorageWorks
HSZ70 Array Controller
HSOF Version 7.0
EK–HSZ70–CG. A01
Digital Equipment Corporation
Maynard, Massachusetts
Configuration Manual

Advertisement

Table of Contents
loading

Related Manuals for Digital Equipment StorageWorks HSZ70

Summary of Contents for Digital Equipment StorageWorks HSZ70

  • Page 1 DIGITAL StorageWorks HSZ70 Array Controller HSOF Version 7.0 EK–HSZ70–CG. A01 Digital Equipment Corporation Maynard, Massachusetts Configuration Manual...
  • Page 2 July 1997 While Digital Equipment Corporation believes the information included in this manual is correct as of the date of publication, it is subject to change without notice. DIGITAL 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.

  • Page 3: Table Of Contents

    Contents Figures ............vii Tables .
  • Page 4 Configuration Manual Setting SCSI Target ID Numbers ....... . . 2-18 Enabling Mirrored Write-Back Cache .
  • Page 5 Replacement Policy ......... . . 3-29 Copy Speed .
  • Page 6 Configuration Manual Deleting a Storageset ......... . 4-18 Changing Switches for a Storageset or Device .

  • Page 7: Figures

    Figures Bridging the Gap Between the Host and Its Storage Subsystem ....1-2 Units Created from Storagesets, Partitions, and Disk Drives ....1-3 Key Controller Components .
  • Page 8 viii Configuration Manual Tables Summary of Controller Features ......1-4 Cache Policies and Cache Module Status ....2-14 Cache Policies and ECB Status .

  • Page 9: Preface

    Preface This book describes the features of the HSZ70 array controller and configuration procedures for the controller and storagesets running HSOF Version 7.0. 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.

  • Page 10: Precautions

    Configuration Manual Precautions Follow these precautions when you’re carrying out the procedures in this book. 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.

  • Page 11: Vhdci Cable Precautions

    Preface 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 you’re connecting cables that use VHDCI connectors: Clean the mating surfaces with a blast of clean air.

  • Page 12: Conventions

    Configuration Manual Conventions This book uses the following typographical conventions and special notices to help you find what you’re looking for. Typographical Conventions Convention Meaning Command syntax that must be entered exactly as ALLCAPS BOLD shown, for example: SET FAILOVER COPY=OTHER_CONTROLLER ALLCAPS Command discussed within text, for example: “Use the SHOW SPARESET command to show the...

  • Page 13: Special Notices

    Preface xiii Special Notices This book doesn’t 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.

  • Page 14: Required Tools

    Configuration Manual Required Tools You’ll need the following tools for servicing the controller, cache module, and external cache battery: A small screwdriver for loosening and tightening the cable- retaining screws. An antistatic wrist strap. An antistatic mat on which to place modules during servicing. An SBB Extractor for removing StorageWorks building blocks.

  • Page 15: Related Publications

    Preface 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.0 EK–CLI70–RM. A01 CLI Reference Manual HSZ70 Array Controller HSOF Version 7.0 EK–HSZ70–CG.

  • Page 16: Revision History

    Configuration Manual Revision History This is a new document.

  • Page 17: Introduction

    1–1 C H A P T E R Introduction This chapter introduces the features and components of the HSZ70 controller.

  • Page 18: Features Of Your Controller

    1–2 Configuration Manual Features of Your Controller Your controller is the intelligent bridge between your host and the devices in your subsystem. From the host’s perspective, the controller is simply another SCSI device connected to one of its I/O buses. Consequently, the host sends its I/O requests to the controller just as it would to any SCSI device.
  • Page 19 Introduction 1–3 You create storage units by combining disk drives into storagesets, such as stripesets, RAIDsets, and mirrorsets, or by presenting them to the host as single-disk units, as shown in Figure 1–2. Stripesets (RAID 0) combine disk drives in serial to increase transfer or request rates.
  • Page 20 1–4 Configuration Manual Table 1–1 summarizes the features of your controller. Table 1–1 Summary of Controller Features Feature Supported Host protocol SCSI–2 Host bus interconnect Wide Ultra Differential SCSI–2 Device protocol SCSI–2 Device bus interconnect Fast Wide Ultra Single-ended SCSI-2 Number of SCSI device ports Number of SCSI device targets per port Maximum number of SCSI devices (with two...
  • Page 21 Introduction 1–5 Table 1–1 Summary of Controller Features (Continued) Feature Supported Maximum number of RAID 5, RAID 1, and RAID 0 storagesets Maximum number of partitions per storageset or disk drive Maximum number of units presented to host 64 (63 if you’re using the StorageWorks Command Console)

  • Page 22: Controller Components

    1–6 Configuration Manual Controller Components Take a few moments to familiarize yourself with the controller’s components shown in Figure 1–3. Figure 1–3 Key Controller Components Control panel Reset button Program-card Host slot Local-connection port port CXO5503B Under normal circumstances, you will not need to remove the controller from its cabinet.

  • Page 23: Key Steps For Configuring Your Subsystem

    Introduction 1–7 Key Steps for Configuring Your Subsystem Figure 1–4 shows the key steps you will follow to set up and configure your subsystem and its controller. Each of these key steps are explained later in this book. Figure 1–4 Overview of Configuring a Subsystem Configure the controller and connect it to the host as described in Chapter 2.

  • Page 25: Configuring An Hsz70 Array Controller

    2–1 C H A P T E R Configuring an HSZ70 Array Controller This chapter contains information about configuring an HSZ70 array controller and the modules that support its operation in a StorageWorks subsystem.

  • Page 26: Introduction

    2–2 Configuration Manual Introduction Unless you specifically requested a preconfigured subsystem, you will have to configure your controller and its subsystem before you can use them. Use the procedure in this chapter to configure your controller. The procedure contains references to more detailed information should you need it.

  • Page 27: Configuring A Controller

    Configuring an HSZ70 Array Controller 2–3 Configuring a Controller You can use this procedure to configure your controller in a single, transparent failover, or multiple-bus failover configuration. Use the references in each step to locate details about the commands and concepts.
  • Page 28 2–4 Configuration Manual The “other controller” inherits “this controller’s” configuration, then restarts. Wait for it to return to normal operation before continuing. See “Selecting a Failover Mode,” page 2-9, for details about failover modes. Skip to step 7. 6. In a transparent failover configuration, if you want to enable mirrored write-back cache, enter this single command: SET THIS_CONTROLLER MIRRORED_CACHE Note Both controllers restart when you set mirror mode.
  • Page 29 Configuring an HSZ70 Array Controller 2–5 See “Using Preferred ID Numbers,” page 2-19, for details about preferred SCSI target ID numbers. 9. Optional: Change the CLI prompt. Use the following syntax: “new prompt” SET THIS_CONTROLLER PROMPT = If you’re configuring dual-redundant controllers, also change the CLI prompt on the “other controller.”...

  • Page 30: Setting The Pva Module Id Switch

    2–6 Configuration Manual See the SHOW THIS_CONTROLLER FULL command in the HSZ70 Array Controller HSOF Version 7.0 CLI Reference Manual for more information about using this command. 14. Connect the controller to the host. See “Connecting a Controller to the Host,” page 2-21, for information about how to complete the connection.

  • Page 31: Establishing A Local Connection To The Controller

    Configuring an HSZ70 Array Controller 2–7 Figure 2–1 SCSI Target IDs and PVA Settings in an Extended Subsystem Enclosure Enclosure Enclosure SCSI Target ID = 3 SCSI Target ID = 11 SCSI Target ID = 15 SCSI Target ID = 2 SCSI Target ID = 10 SCSI Target ID = 14 SCSI Target ID = 1...
  • Page 32 2–8 Configuration Manual Figure 2–2 Terminal to Local-Connection Port Connection DEConnect office cable Local connection port RJ-11 adapter PC serial-port adapter RJ-11 extension cable CXO5611A Caution The local-connection port described in this book generates, uses, and can radiate radio-frequency energy through cables that are connected to it.

  • Page 33: Selecting A Failover Mode

    Configuring an HSZ70 Array Controller 2–9 3. Configure the terminal for 19200 baud, 8 data bits, 1 stop bit, and no parity. 4. Press the Enter or Return key. A copyright notice and the CLI prompt appear, indicating that you established a local connection with the controller.

  • Page 34: Selecting A Cache Mode

    2–10 Configuration Manual Balance your assignment of target IDs across your dual-redundant pair of controllers for better subsystem performance. For example, if you are presenting four targets to the host, prefer two to one controller and two to the other controller. Balance your assignment of devices.
  • Page 35 Configuring an HSZ70 Array Controller 2–11 through caching for some units while enabling only write-back caching for other units. Increasing Read Performance Read Caching This caching technique decreases the subsystem’s response time to a read request by allowing the controller to satisfy the request from the cache memory rather than from the disk drives.
  • Page 36 2–12 Configuration Manual Increasing Write Performance Write-Back Caching This caching technique decreases the subsystem’s response time to write requests by allowing the controller to declare the write operation complete as soon as the data reaches its cache memory. The controller performs the slower operation of writing the data to the disk drives at a later time.
  • Page 37 Configuring an HSZ70 Array Controller 2–13 Note The controller executes multiple write operations to satisfy a single write request for a RAIDset or mirrorset. For this reason, a RAIDset or mirrorset requires non-volatile cache memory to ensure data redundancy until the write request is satisfied. Regardless of the back-up power source you choose, the cache- memory power LED flashes about once every three seconds to indicate the cache module’s memory array is receiving power from its primary...

  • Page 38: Cache Policies And Cache Module Status

    2–14 Configuration Manual Figure 2–3 Mirrored Caching Cache module A Cache module B cache cache Copy of Copy of cache cache CXO5729A Dynamic Caching Techniques If the controller detects a full or partial failure of its cache module or ECB, it automatically reacts to preserve the cached write-back data. Then, depending upon the severity of the failure, the controller chooses an interim caching technique—also called the cache policy—which it uses until you repair or replace the cache module or its ECB.
  • Page 39 Configuring an HSZ70 Array Controller 2–15 Table 2–1 Cache Policies and Cache Module Status (Continued) Cache Module Status Cache Policy Cache A Cache B Unmirrored Cache Mirrored Cache Multibit Good Data loss: Forced error and loss of Data loss: No. Controller A cache write-back data for which multibit error recovers its lost write-back data...

  • Page 40: Cache Policies And Ecb Status

    2–16 Configuration Manual Table 2–1 Cache Policies and Cache Module Status (Continued) Cache Module Status Cache Policy Cache A Cache B Unmirrored Cache Mirrored Cache Cache Good Same as for SIMM failure. Data loss: No. Controller A board recovers all of its write-back data failure from the mirrored copy on cache B.
  • Page 41 Configuring an HSZ70 Array Controller 2–17 Table 2–2 Cache Policies and ECB Status (Continued) ECB Status Cache Policy Unmirrored Cache Mirrored Cache Cache A Cache B Good Data loss: No. Data loss: No. Cache policy: Controller A supports Cache policy: Both controllers write-through caching only;...

  • Page 42: Setting Scsi Target Id Numbers

    2–18 Configuration Manual Table 2–2 Cache Policies and ECB Status (Continued) ECB Status Cache Policy Unmirrored Cache Mirrored Cache Cache A Cache B Failed Data loss: No. Data loss: No. Cache policy: Both controllers support Cache policy: Both controllers support write-through caching only.

  • Page 43: Enabling Mirrored Write-Back Cache

    Configuring an HSZ70 Array Controller 2–19 Figure 2–1 on page 2-7 illustrates the SCSI target ID numbers and PVA settings for subsystems. Device addressing which allows the controller to identify the location of devices based on a port-target-LUN (PTL) number is described in “Device PTL Addressing Convention within the Controller,”...

  • Page 44: Changing The Cli Prompt

    2–20 Configuration Manual operation, each controller services only those storage units that are associated with its preferred ID numbers. You can also use the PREFERRED_ID switch to effectively make the “other controller” a hot standby by declaring that it has no preferred SCSI target ID.

  • Page 45: Selecting A Host Compatibility Mode

    Configuring an HSZ70 Array Controller 2–21 in the event of a primary power failure. See the HSZ70 Array Controller HSOF Version 7.0 CLI Reference Manual for details about the SET THIS_CONTROLLER CACHE_UPS command. See Table 2– 1 on page 2-14 and Table 2–2 on page 2-16 for information about cache policies.
  • Page 46 2–22 Configuration Manual If you’re connecting a host to a controller in any other enclosure or cabinet, skip to step 5. Figure 2–4 Connecting a Single Controller to Its Host Backplane connector Program-card slot Program-card ejection button Program card ESD cover Operator Ferrite bead Local...
  • Page 47 Configuring an HSZ70 Array Controller 2–23 Connecting Dual-redundant Controllers to the Host To connect a pair of dual-redundant controllers to the host: 1. Stop all I/O from the host to its devices on the bus to which you are connecting the controllers. 2.
  • Page 48 2–24 Configuration Manual 7. Reconnect the trilink connectors to the host ports on the controllers. Do not disconnect the host cables from the trilink connector. 8. Route and tie the cables as desired. 9. Restart the I/O from the host. Some operating systems may require you to restart the host to see the devices attached to the new controller.
  • Page 49 Configuring an HSZ70 Array Controller 2–25 Figure 2–6 Connecting Multiple Bus Failover, Dual-Redundant Controllers to the Host Trilink Bus cable connector from host Ferrite bead Trilink connector cable Terminator Ferrite or host bus bead cable Terminator or host bus cable CXO5613A 5.

  • Page 51: Planning Storagesets

    3–1 C H A P T E R Planning Storagesets This chapter provides information to help you create a storageset profile for your subsystem. Each storageset type is described as well as the switches you can set for each type.

  • Page 52: Creating A Storageset And Device Profile

    3–2 Configuration Manual Creating a Storageset and Device Profile Creating a profile for your storagesets and devices can help simplify the configuration process. This chapter helps you to choose the storagesets that best suit your needs and to make informed decisions about the switches that you can enable for each storageset or storage device that you configure in your subsystem.
  • Page 53 Planning Storagesets 3–3 Figure 3–1 A Typical Storageset Profile...

  • Page 54: Determining Storage Requirements

    3–4 Configuration Manual Determining Storage Requirements Start the planning process by determining your storage requirements. Here are a few of the questions you should ask yourself: What applications or user groups will access the subsystem? How much capacity do they need? What are the I/O requirements? If an application is data-transfer intensive, what is the required transfer rate? If it is I/O-request intensive, what is the required response time? What is the read/...

  • Page 55: Choosing A Storageset Type

    Planning Storagesets 3–5 Choosing a Storageset Type Different applications may have different storage requirements, so you will probably want to configure more than one kind of storageset in your subsystem. All of the storagesets described in this book implement RAID (Redundant Array of Independent Disks) technology.

  • Page 56: Using Stripesets To Increase I/O Performance

    3–6 Configuration Manual Using Stripesets to Increase I/O Performance Stripesets enhance I/O performance by spreading the data across multiple disk drives. Each I/O request is broken into small segments called “chunks.” These chunks are then “striped” across the disk drives in the storageset, thereby allowing several disk drives to participate in one I/O request to handle several I/O requests simultaneously.

  • Page 57: Considerations For Planning A Stripeset

    Planning Storagesets 3–7 Considerations for Planning a Stripeset Keep the following points in mind as you plan your stripesets: Reporting methods and size limitations prevent certain operating systems from working with large stripesets. See the StorageWorks Array Controller HSZ70 Array Controller Operating Software HSOF Version 7.0 Release Notes or the Getting Started Guide that came with your platform kit for details about these restrictions.
  • Page 58 3–8 Configuration Manual Stripesets are not well-suited for the following applications: A storage solution for data that cannot be easily reproduced or for data that must be available for system operation Applications that make requests for small amounts of sequentially located data Applications that make synchronous random requests for small amounts of data Figure 3–3 Distribute Members across Ports...

  • Page 59: Using Mirrorsets To Ensure Availability

    Planning Storagesets 3–9 Using Mirrorsets to Ensure Availability Mirrorsets use redundancy to ensure availability, as illustrated in Figure 3–4. For each primary disk drive, there is at least one mirror disk drive. Thus, if a primary disk drive fails, its mirror drive immediately provides an exact copy of the data.
  • Page 60 3–10 Configuration Manual If you’re using more than one mirrorset in your subsystem, you should put the first member of each mirrorset on different buses as shown in Figure 3–5. (The first member of a mirrorset is the first disk drive you add.) When a controller receives a request to read or write data to a mirrorset, it typically accesses the first member of the mirrorset.
  • Page 61 Planning Storagesets 3–11 Mirrorsets are well-suited for the following: Any data for which reliability requirements are extremely high Data to which high-performance access is required Applications for which cost is a secondary issue Mirrorsets are not well-suited for the following applications: Write-intensive applications Applications for which cost is a primary issue...

  • Page 62: Using Raidsets To Increase Performance And Availability

    3–12 Configuration Manual Using RAIDsets to Increase Performance and Availability RAIDsets are enhanced stripesets—they use striping to increase I/O performance and distributed-parity data to ensure data availability. Figure 3–6 illustrates the concept of RAIDsets and parity data. Figure 3–6 Parity Ensures Availability; Striping Provides Good Performance I/O Request Chunk 1...

  • Page 63: Considerations For Planning A Raidset

    Planning Storagesets 3–13 The relationship between the chunk size and the average request size determines if striping maximizes the request rate or the data-transfer rates. You can set the chunk size or let the controller set it automatically. See “Chunk Size,” page 3-33, for information about setting the chunk size.
  • Page 64 3–14 Configuration Manual RAIDsets are not particularly well-suited for the following: Write-intensive applications Applications that require high data transfer capacity High-speed data collection Database applications in which fields are continually updated Transaction processing...

  • Page 65: Using Striped Mirrorsets For Highest Performance And Availability

    Planning Storagesets 3–15 Using Striped Mirrorsets for Highest Performance and Availability Striped mirrorsets are simply stripesets whose members are mirrorsets. Consequently, this kind of storageset combines the performance of striping with the reliability of mirroring. The result is a storageset with very high I/O performance and high data availability.

  • Page 66: Naming Storagesets And Units

    3–16 Configuration Manual Naming Storagesets and Units Configure storagesets manually if you want to use your own naming scheme. StorageWorks Command Console and CFMENU name each storageset using a simple naming convention. Command Console and CFMENU also automatically provide unit-number prefixes and allow you to specify the actual number.

  • Page 67: Assigning Unit Numbers For Host Access To Storagesets

    Planning Storagesets 3–17 Assigning Unit Numbers for Host Access to Storagesets A controller supports up to eight SCSI target IDs, each of which can present up to eight logical unit numbers (LUNs) to a host. This means that each controller or dual-redundant pair of controllers can present up to 64 storage units to a host.
  • Page 68 3–18 Configuration Manual Omit the leading zeroes for storage units associated with the controller’s SCSI target ID zero. For example, use D2 instead of D002 for a storageset that’s accessed through LUN 2 of the controller’s SCSI target ID 0. Table 3–2 shows additional unit numbering examples.

  • Page 69: Creating A Storageset Map

    Planning Storagesets 3–19 Creating a Storageset Map Configuring your subsystem will be easier if you know how the storagesets correspond to the disk drives in your subsystem. You can see this relationship by creating a storageset map like the one shown in Figure 3–8 on page 3-19.

  • Page 70: Device Ptl Addressing Convention Within The Controller

    3–20 Configuration Manual 2. Establish a local or remote connection to one of the controllers in your subsystem. 3. Show the devices that are assigned to the controller. Use the following syntax: SHOW DEVICES 4. Locate each device assigned to the controller and record its location on your copy of the cabinet template.
  • Page 71 Planning Storagesets 3–21 Note The controller operates with BA370 rack-mountable enclosures assigned enclosure ID numbers 0, 2, and 3. You set these ID numbers using the PVA module. Enclosure ID number 1, which houses devices at targets 4 through 7, is not supported. Do not use device target ID numbers 4 through 7 in a storage subsystem.
  • Page 72 10000 10100 10200 10300 20000 20100 20200 20300 30000 30100 30200 30300 40000 40100 40200 40300 50000 50100 50200 50300 60000 60100 60200 60300 10800 10900 11000 11100 20800 20900 21000 21100 30800 30900 31000 31100 40800 40900 41000 41100 50800 50900 51000...
  • Page 73 Planning Storagesets 3–23 In Figure 3–10 the controller addresses DISK30800 through device port 3, target 08, LUN 00. This PTL location indicates the pathway the controller uses to address a disk or tape drive (device) in the subsystem. It also indicates the device name. The controller uses the PTL location to name each device that you add to your subsystem with StorageWorks Command Console, the CONFIG utility, or CFMENU.

  • Page 74: Planning Partitions

    3–24 Configuration Manual Planning Partitions Use partitions to divide a storageset or disk drive into smaller pieces, each of which can be presented to the host as its own storage unit. Figure 3–12 shows the conceptual effects of partitioning a single-disk unit.

  • Page 75: Guidelines For Partitioning Storagesets And Disk Drives

    Planning Storagesets 3–25 Guidelines for Partitioning Storagesets and Disk Drives Keep these points in mind as you plan your partitions: You can create up to eight partitions per storageset or disk drive. All of the partitions on the same storageset or disk drive must be addressed through the same target ID (host-addressable SCSI ID.) Thus, if you set a preferred controller for that ID, all the partitions in that storageset will inherit that preferred controller.

  • Page 76: Choosing Switches For Storagesets And Devices

    3–26 Configuration Manual Choosing Switches for Storagesets and Devices Depending upon the kind of storageset or device you are configuring, you can enable the following kinds of options or “switches”: RAIDset and mirrorset switches Initialize switches Unit switches Device switches Enabling Switches If you use StorageWorks Command Console to configure the device or storageset, you can set switches from the command console screens...

  • Page 77: Raidset Switches

    Planning Storagesets 3–27 RAIDset Switches You can enable the following kinds of switches to control how a RAIDset behaves to ensure data availability: Replacement policy Reconstruction policy Membership Replacement Policy Specify a replacement policy to determine how the controller replaces a failed disk drive: POLICY=BEST_PERFORMANCE (default) puts the failed disk drive in the failedset then tries to find a replacement (from the...

  • Page 78: Membership

    3–28 Configuration Manual Membership Indicate to the controller that the RAIDset you are adding is either complete or reduced, which means it is missing one of its members: NOREDUCED (default) indicates to the controller that all of the disk drives are present for a RAIDset. REDUCED lets you add a RAIDset that is missing one of its members.

  • Page 79: Mirrorset Switches

    Planning Storagesets 3–29 Mirrorset Switches You can enable the following switches to control how a mirrorset behaves to ensure data availability: Replacement policy Copy speed Read source Replacement Policy Specify a replacement policy to determine how the controller replaces a failed disk drive: POLICY=BEST_PERFORMANCE (default) puts the failed disk drive in the failedset then tries to find a replacement (from the spareset) that is on a different device port than the remaining,...

  • Page 80: Read Source

    3–30 Configuration Manual Read Source Specify the read source to determine how the controller reads data from the members of a mirrorset: READ_SOURCE=LEAST_BUSY (default) forces the controller to read data from the “normal” or operational member that has the least-busy work queue. READ_SOURCE=ROUND_ROBIN forces the controller to read data sequentially from all “normal”...

  • Page 81: Device Switches

    Planning Storagesets 3–31 Device Switches When you add a disk drive or other storage device to your subsystem, you can enable the following switches: Transportability Transfer rate Transportability Indicate whether a disk drive is transportable when you add it to your subsystem: NOTRANSPORTABLE disk drives (default) are marked with StorageWorks-exclusive metadata.

  • Page 82: Transfer Rate

    3–32 Configuration Manual Can be interchanged with any SCSI interface that does not use the device metadata, for example, a PC. Cannot have write-back caching enabled. Cannot be members of a shadowset, storageset, or spareset. Do not support forced errors. Consider these points when using the TRANSPORTABLE switch: Before you move devices from the subsystem to a foreign subsystem, delete the units and storagesets associated with the...

  • Page 83: Initialize Switches

    Planning Storagesets 3–33 Initialize Switches You can enable the following kinds of switches to affect the format of a disk drive or storageset: Chunk size (for stripesets and RAIDsets only) Save configuration Overwrite After you initialize the storageset or disk drive, you cannot change these switches without reinitializing the storageset or disk drive.
  • Page 84 3–34 Configuration Manual requests. Thus, in principle, separate I/O requests can be handled in parallel, thereby increasing the request rate. This concept is shown in Figure 3–13. Figure 3–13 Chunk Size Larger than the Request Size Chunk size = 128k (256 blocks) Request A Request B Request C...

  • Page 85: Maximum Chunk Sizes For A Raidset

    Planning Storagesets 3–35 Figure 3–14 Chunk Size Smaller than the Request Size Chunk size = 128k (256 blocks) Request A CXO-5172A-MC Applications such as CAD, image processing, data collection and reduction, and sequential file processing tend to require high data- transfer rates.

  • Page 86: Save Configuration

    3–36 Configuration Manual Table 3–3 Maximum Chunk Sizes for a RAIDset (Continued) RAIDset Size Max Chunk Size 4 members 682 blocks 5 members 512 blocks 6 members 409 blocks 7 members 341 blocks 8 members 292 blocks 9 members 256 blocks 10 members 227 blocks 11 members...
  • Page 87 Planning Storagesets 3–37 The save configuration option saves the following information: All configuration information normally saved when you restart your controller except, the controller serial number, product ID number, vendor ID number, and any manufacturing fault information. Patch information The save configuration option does not save the following information: Software or hardware upgrades Inter-platform conversions...

  • Page 88: Destroy/Retain

    3–38 Configuration Manual If you previously configured storagesets with the SAVE_CONFIGURATION option, you do not need to initialize them again after you reconfigure your devices with a new controller. When you replace a controller, make sure the replacement controller does not contain any configuration data. If the controller is not new, initialize it with the SET THIS_CONTROLLER INITIAL_CONFIGURATION command.
  • Page 89 Planning Storagesets 3–39 striped mirrorsets and mirrorsets. DESTROY (default) overwrites the user data and forced-error metadata on a disk drive when it is initialized. NODESTROY preserves the user data and forced-error metadata when a disk drive is initialized. Use NODESTROY to create a single-disk unit from any disk drive that has been used as a member of a mirrorset.

  • Page 90: Unit Switches

    3–40 Configuration Manual Unit Switches You can enable the Unit switches listed in Table 3–4 for the listed storagesets and devices. See the HSZ70 Array Controller HSOF Version 7.0 CLI Reference Manual for a complete list of Unit switches. Table 3–4 ADD UNIT Switches for Storagesets Container Type RAIDset...

  • Page 91: Partition

    Planning Storagesets 3–41 In a multiple host environment specifying access IDs prevents multiple hosts from accessing the same unit. Use this feature on a unit-by-unit basis to ensure units are accessed only by the host for which they are configured. The access ID for a passthrough unit is always ALL;...

  • Page 92: Preferred Path For Multiple-Bus Failover Configurations

    3–42 Configuration Manual The MAXIMUM_CACHED_TRANSFER switch affects both read and write-back cache when set on a controller that has read and write- back caching. Preferred Path for Multiple-Bus Failover Configurations The PREFERRED PATH switch applies only to storage units in a multiple-bus failover configuration.

  • Page 93: Write Protection

    Planning Storagesets 3–43 RUN (default) specifies that as soon as you provide a host- addressable unit number the storage unit will be made available to the host. NORUN specifies that the storage unit will not be made available to the host until you specify the RUN switch. Write Protection Enable or disable write protection for the storage unit: NOWRITE_PROTECT (default) enables the controller to write...

  • Page 94: Moving Storagesets

    3–44 Configuration Manual Moving Storagesets You can move a storageset from one subsystem to another without destroying its data. You also can follow these steps to move a storageset to a new location within the same subsystem. Figure 3–15 Moving a Storageset from one Subsystem to Another CXO5595A Caution Never initialize any container or this procedure will not protect data.
  • Page 95 Planning Storagesets 3–45 3. Delete the unit-number shown in the “Used by” column of the SHOW storageset-name command. Use the following syntax: unit-number DELETE 4. Delete the storageset shown in the “Name” column of the SHOW storageset-name command. Use the following syntax: storageset-name DELETE 5.
  • Page 96 3–46 Configuration Manual DELETE D100 DELETE RAID99 DELETE DISK10000 DELETE DISK20000 DELETE DISK30000 (...move the disk drives to their new location...) ADD DISK DISK20000 2 0 0 ADD DISK DISK30000 3 0 0 ADD DISK DISK40000 4 0 0 ADD RAIDSET RAID99 DISK20000 DISK30000 DISK40000 ADD UNIT D100 RAID99 Example 3–2 The following example moves the reduced RAIDset, R3, to another...

  • Page 97: The Next Step

    Planning Storagesets 3–47 The Next Step... Turn to the section “Automatically Configuring Storagesets with CFMENU,” page 4-21, if you want to configure your storage units automatically with CFMENU, a menu-based utility that simplifies the configuration process. This utility is especially helpful if you are configuring storagesets for the first time.

  • Page 99: Configuring Storagesets

    4–1 C H A P T E R Configuring Storagesets The preferred method for configuring storagesets is to use StorageWorks Command Console. Getting Started with Command Console provides a description of the application and how to use it to configure storagesets. StorageWorks Command Console is a Graphical User Interface (GUI) for the set up and management of RAID storage subsystems.

  • Page 100: Manually Configuring Storagesets

    4–2 Configuration Manual Manually Configuring Storagesets One method of configuring storagesets is manual configuration. This method allows you the most flexibility in defining and naming storagesets. See the HSZ70 Array Controller HSOF Version 7.0 CLI Reference Manual for complete information about the CLI commands shown in this chapter.

  • Page 101: Initialize Switches For Stripesets

    Configuring Storagesets 4–3 Table 4–1 contains the valid Initialize switches and values. Table 4–1 Initialize Switches for Stripesets Initialize Switch Value and Syntax Chunk size CHUNKSIZE=DEFAULT* CHUNKSIZE=N Save configuration NOSAVE_CONFIGURATION* SAVE_CONFIGURATION Destroy NODESTROY* DESTROY 3. Present the stripeset to the host by giving it a unit number the host can recognize.

  • Page 102: Configuring A Mirrorset

    4–4 Configuration Manual 5. Verify the unit configuration and switches. Use the following syntax: unit-number SHOW Example 4–1 The following example shows the commands you would use to create Stripe1, a three-member stripeset: ADD STRIPESET STRIPE1 DISK10000 DISK20000 DISK30000 INITIALIZE STRIPE1 CHUNKSIZE=128 ADD UNIT D100 STRIPE1 MAXIMUM_CACHED_TRANSFER=16 WRITEBACK_CACHE SHOW STRIPE1...

  • Page 103: Initialize Switches For Mirrorsets

    Configuring Storagesets 4–5 Table 4–3 Mirrorset Switches (Continued) Mirrorset Switch Value and Syntax Read source READ_SOURCE=LEAST_BUSY* READ_SOURCE=ROUND_ROBIN READ_SOURCE=DISKnnnnn 2. Initialize the mirrorset. If you want to set any Initialize switches, you must do so in this step. Use the following syntax: mirrorset-name switch INITIALIZE Table 4–4 contains the valid Initialize switches and values.

  • Page 104: Configuring A Raidset

    4–6 Configuration Manual Table 4–5 Unit Switches for Mirrorsets (Continued) Unit Switch Value and Syntax Availability RUN* NORUN Access protection ACCESS_ID=ALL* ACCESS_ID=nn 4. Verify the mirrorset configuration and switches. Use the following syntax: mirrorset-name SHOW 5. Verify the unit configuration and switches. Use the following syntax: unit-number SHOW Example 4–2...

  • Page 105: Raidset Switches

    Configuring Storagesets 4–7 Table 4–6 contains the valid RAIDset switches and values. Table 4–6 RAIDset Switches RAIDset Switch Value and Syntax Replacement policy POLICY=BEST_PERFORMANCE* POLICY=BEST_FIT NOPOLICY Reconstruction speed RECONSTRUCT=NORMAL* RECONSTRUCT=FAST 2. Initialize the RAIDset. Optional: If you want to set the Initialize switches, you must do so in this step.

  • Page 106: Unit Switches For Raidsets

    4–8 Configuration Manual Table 4–8 contains the valid Unit switches and values. Table 4–8 Unit Switches for RAIDsets Unit switch Value and syntax Maximum cached MAXIMUM_CACHED_TRANSFER=32* transfer MAXIMUM_CACHED_TRANSFER=n Read cache READ_CACHE* NOREAD_CACHE Write-back cache NOWRITEBACK_CACHE* WRITEBACK_CACHE Write protection NOWRITE_PROTECT* WRITE_PROTECT Availability RUN* NORUN...

  • Page 107: Initialize Switches For Striped Mirrorsets

    Configuring Storagesets 4–9 To configure a striped mirrorset: 1. Create—but do not initialize—at least two mirrorsets. 2. Create a stripeset and specify the mirrorsets it contains. Use the following syntax: mirrorset_1 mirrorset_2 ADD STRIPESET 3. Initialize the stripeset. If you want to set any Initialize switches, you must do so in this step.

  • Page 108: Configuring A Single-Disk Unit

    4–10 Configuration Manual Table 4–10 Unit Switches for Striped Mirrorsets (Continued) Unit Switch Value and Syntax Write protection NOWRITE_PROTECT* WRITE_PROTECT Availability RUN* NORUN Access protection ACCESS_ID=ALL* ACCESS_ID=nn 5. Verify the striped mirrorset configuration and switches. Use the following syntax: stripeset-name SHOW 6.

  • Page 109: Device Switches For Single-Disk Units

    Configuring Storagesets 4–11 Table 4–11 contains the valid Device switches and values. Table 4–11 Device Switches for Single-Disk Units Device Switch Value and Syntax Transportability NOTRANSPORTABLE* TRANSPORTABLE Transfer rate TRANSFER_RATE_REQUESTED=20MHZ* TRANSFER_RATE REQUESTED=10MHZ TRANSFER_RATE_REQUESTED=5MHZ TRANSFER_RATE_REQUESTED=ASYNCHRO- NOUS 2. Initialize the disk drive using the following syntax: nnn switch INITIALIZE DISK 3.

  • Page 110: Configuring A Tape Drive

    4–12 Configuration Manual Note If you make a disk transportable, you cannot specify WRITEBACK_CACHE for that disk. 4. Verify the configuration using the following command: SHOW DEVICES Example 4–5 The following example shows the commands you would use to configure DISK10000 as a single-disk unit. ADD DISK DISK10000 1 0 0 ADD UNIT D101 DISK10000 SHOW DEVICES...

  • Page 111: Configuring A Tape Loader

    Configuring Storagesets 4–13 Example 4–6 The following example shows the commands you would use to create a passthrough device for controlling a tape drive: ADD PASSTHROUGH TAPE10000 1 0 0 ADD UNIT P100 TAPE10000 passthrough-name SHOW Configuring a Tape Loader The controller handles devices such as tape loaders as passthrough devices.

  • Page 112: Partitioning A Storageset Or Disk Drive

    4–14 Configuration Manual Example 4–7 The following example shows the commands you would use to create a passthrough device for controlling a tape loader: ADD PASSTHROUGH LDR10300 1 3 0 ADD UNIT P130 LDR10300 SHOW PASSTHROUGH Partitioning a Storageset or Disk Drive See “Planning Partitions,”...

  • Page 113: Unit Switches For Partitioned Storagesets And Disk Drives

    Configuring Storagesets 4–15 Use the following syntax to present partitions to the host: unit-number storageset-name partition-number ADD UNIT PARTITION= switch Table 4–13 contains the valid Unit switches and values for partitioned storagesets and disk drives. Table 4–13 Unit Switches for Partitioned Storagesets and Disk Drives Unit Switch Value and Syntax...

  • Page 114: Adding A Disk Drive To The Spareset

    4–16 Configuration Manual Partition number Size Starting Block Used by 1915 (0.98 MB) 0 1915 (0.98 MB) 1920 1915 (0.98 MB) 3840 2371 (1.21 MB) 5760 ADD UNIT D1 RAID1 PARTITION=1 WRITEBACK_CACHE ADD UNIT D2 RAID1 PARTITION=2 WRITEBACK_CACHE ADD UNIT D3 RAID1 PARTITION=3 WRITEBACK_CACHE ADD UNIT D4 RAID1 PARTITION=4 WRITEBACK_CACHE SHOW RAID1 Partition number Size...

  • Page 115: Removing A Disk Drive From The Spareset

    Configuring Storagesets 4–17 1. Add the disk drive to the controller’s spareset list. Use the following syntax: nnnnn ADD SPARESET DISK Repeat this step for each disk drive you want to add to the spareset: 2. Verify the contents of the spareset using the following syntax: SHOW SPARESET Example 4–9 The following example shows the commands you would use to add...

  • Page 116: Enabling Autospare

    4–18 Configuration Manual DELETE SPARESET DISK60000 SHOW SPARESET Name Storageset Uses Used by SPARESET spareset disk60100 Enabling Autospare With AUTOSPARE enabled on the failedset, any new disk drive that is inserted into the PTL location of a failed disk drive is automatically initialized and placed into the spareset.

  • Page 117: Changing Switches For A Storageset Or Device

    Configuring Storagesets 4–19 4. Verify the configuration using the following syntax: SHOW STORAGESETS Example 4–11 The following example shows the commands you would use to delete Stripe1, a three-member stripeset that comprises DISK10000, DISK20000, and DISK30000. SHOW STORAGESETS Name Storageset Uses Used by STRIPE1...
  • Page 118 4–20 Configuration Manual Changing Device Switches Use the SET command to change the device switches. For example, the following command enables DISK10000 to be used in a non- StorageWorks environment: SET DISK10000 TRANSPORTABLE The TRANSPORTABLE switch cannot be changed for a disk if the disk is part of an upper-level container.

  • Page 119: Automatically Configuring Storagesets With Cfmenu

    Configuring Storagesets 4–21 Automatically Configuring Storagesets with CFMENU StorageWorks Command Console is the preferred method for automatically configuring storagesets and devices. See Getting Started with Command Console, for details about using it for configuration. CFMENU is an effective utility that simplifies the task of configuring storagesets and devices.
  • Page 120 4–22 Configuration Manual Table 4–14 lists the heading and contents for each column on the Main Menu. Table 4–14 Interpreting CFMENU Columns Column Heading Information Displayed Main menu Shows the tasks you can accomplish with CFMENU. Unconfig’d Dev.PTLs Shows the PTL locations of devices that have not yet been added to the controller’s configu- ration.

  • Page 121: Considerations For Using Cfmenu

    Configuring Storagesets 4–23 Table 4–14 Interpreting CFMENU Columns (Continued) Column Heading Information Displayed Unit Shows the unit numbers for all storagesets or devices. Displays “P” if the unit is partitioned. Displays “Y” if the unit is write protected. Displays “Y” if you enabled write-back cache. Considerations for Using CFMENU Keep the following points in mind for using CFMENU: CFMENU names each storageset according to a simple naming...

  • Page 122: Creating A Storageset With Cfmenu

    4–24 Configuration Manual 2. Start CFMENU using the following syntax: RUN CFMENU 3. From the Main Menu, choose task 1 to go to the Device Menu. 4. From the Device Menu, choose task 1 to add disk drives. 5. CFMENU presents—one at a time—the disk drives or devices that you may add to the subsystem.

  • Page 123: Deleting A Storageset With Cfmenu

    Configuring Storagesets 4–25 7. CFMENU displays a message that indicates the storageset’s type and name, as well as the names of all its members. Press Return to create the storageset. 8. Return to the Main Menu and repeat step 2 through step 7 for each storageset or single-disk unit you want to create.

  • Page 124: Adding A Disk Drive To The Spareset With Cfmenu

    4–26 Configuration Manual Adding a Disk Drive to the Spareset with CFMENU To add a disk drive to the spareset: 1. Start CFMENU using the following syntax: RUN CFMENU 2. From the Main Menu, choose task 4 to go to the RAIDset Menu. 3.

  • Page 125: Periodic Procedures

    5–1 C H A P T E R Periodic Procedures This chapter describes procedures you might need to use when working with your HSZ70 array controller: formatting a disk, cloning data for backup, backing up your configuration, restarting your subsystem, and shutting down your subsystem.

  • Page 126: Formatting Disk Drives

    5–2 Configuration Manual Formatting Disk Drives Use HSUTIL’s FORMAT option to simultaneously format up to seven disk drives attached to a single controller or up to six disk drives attached to a dual-redundant pair of controllers. Consider the following points before formatting disk drives with HSUTIL: HSUTIL cannot format disk drives configured as single-disk drive units or as members of a storageset, spareset, or failedset.
  • Page 127 Periodic Procedures 5–3 4. Enter Y to enter another disk drive name or N to begin the formatting operation. 5. Read the cautionary information that HSUTIL displays, then confirm or cancel the formatting operation. The formatting operation will complete in approximately the estimated time.
  • Page 128 5–4 Configuration Manual DESTINATION DEVICE(S). IF A SCSI BUS RESET OCCURS, THE FORMAT MAY BE INCOMPLETE AND YOU MAY HAVE TO RE-INVOKE HSUTIL. AFTER YOU ANSWER THE NEXT QUESTION, THE FORMAT WILL START. DO YOU WANT TO CONTINUE (Y/N) [N] ? Y HSUTIL STARTED AT: 14-JAN-1997 15:00:31 FORMAT OF DISK10000 FINISHED AT 14-JAN-1997 15:25:12 FORMAT OF DISK20000 FINISHED AT 14-JAN-1997 15:30:31...

  • Page 129: Cloning Data For Backup

    Periodic Procedures 5–5 Cloning Data for Backup Use the CLONE utility to duplicate the data on any unpartitioned single-disk unit, stripeset, mirrorset, or striped mirrorset in preparation for backup. When the cloning operation is done, you can back up the clones rather than the storageset or single-disk unit, which can continue to service its I/O load.
  • Page 130 5–6 Configuration Manual Figure 5–1 CLONE Steps for Duplicating Unit Members Unit Unit Temporary mirrorset Disk10300 New member Disk10300 Unit Temporary mirrorset Unit New member Disk10300 Disk10300 Clone Unit Clone of Disk10300 CXO5510A To clone a single-disk unit, stripeset, or mirrorset: 1.
  • Page 131 Periodic Procedures 5–7 6. When prompted, enter the disk drives you want to use for the clone units. 7. Back up the clone unit. Example 5–2 This example shows the commands you would use to clone storage unit D204. The clone command terminates after it creates storage unit D205, a clone or copy of D204.
  • Page 132 5–8 Configuration Manual USE AVAILABLE DEVICE DISK20400(SIZE=832317) FOR MEMBER DISK20000(SIZE=832317) (Y,N) [Y] ? Y MIRROR DISK20000 C_MB SET C_MB NOPOLICY SET C_MB MEMBERS=2 SET C_MB REPLACE=DISK20400 COPY IN PROGRESS FOR EACH NEW MEMBER. PLEASE BE PATIENT... COPY FROM DISK10300 TO DISK20200 IS 100% COMPLETE COPY FROM DISK20000 TO DISK20400 IS 100% COMPLETE PRESS RETURN WHEN YOU WANT THE NEW UNIT TO BE CREATED REDUCE DISK20200 DISK20400...

  • Page 133: Backing Up Your Subsystem Configuration

    Periodic Procedures 5–9 Backing Up Your Subsystem Configuration Your controller stores information about your subsystem configuration in its nonvolatile memory. This information could be lost if the controller fails or when you replace a module in your subsystem. You can avoid reconfiguring your subsystem manually by saving configuration information on one or more of your subsystem disks using the INITIALIZE SAVE_CONFIGURATION command.

  • Page 134: Saving Subsystem Configuration Information To A Storageset

    5–10 Configuration Manual Saving Subsystem Configuration Information to a Storageset You can save your subsystem configuration information to a storageset. The configuration information is duplicated on every disk that is a member of the storageset. Use the following syntax: storageset-name INITIALIZE SAVE_CONFIGURATION Displaying the Status of the Save Configuration Feature...
  • Page 135 Periodic Procedures 5–11 The following example shows sample devices with the SAVE_CONFIGURATION switch enabled: $ SHOW DEVICES FULL Name Type Port Targ Used by ------------------------------------------------------------------------------ DISK10000 disk RZ28M (C) DEC 1003 Switches: NOTRANSPORTABLE TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 10.00 MHZ negotiated) Size: 4108970 blocks Configuration being backed up on this container DISK30300...

  • Page 136: Shutting Down Your Subsystem

    5–12 Configuration Manual Shutting Down Your Subsystem Follow these steps to shut down your StorageWorks subsystem: 1. On the host, dismount the storage units in your subsystem. 2. Connect a maintenance terminal to one of the controllers in your subsystem. 3.

  • Page 137: Restarting Your Subsystem

    Periodic Procedures 5–13 Restarting Your Subsystem Follow these steps to restart your subsystem: 1. Plug in the subsystem’s power cord. 2. Turn on the subsystem. 3. Press and hold the reset button on the controller for three seconds, then release it. 4.

  • Page 139: Appendix A: Controller Specifications

    A–1 A P P E N D I X Controller Specifications This appendix contains physical, electrical, and environmental specifications for the HSZ70 array controller.

  • Page 140: Physical And Electrical Specifications For The Controller

    A–2 Configuration Manual Physical and Electrical Specifications for the Controller Table A–1 lists the physical and electrical specifications for the controller and cache modules. Table A–1 Controller Specifications Current at Current at Hardware Length Width Power +5 V +12 V HSZ70 Array Controller 12.5 inches 8.75 inches...

  • Page 141: Environmental Specifications

    A–3 Environmental Specifications The HSZ70 array controller is intended for installation in a Class A computer room environment. The environmental specifications listed in Table A–2 are the same as for other DIGITAL storage devices. Table A–2 StorageWorks Environmental Specifications Condition Optimum Operating Environment Temperature +18°...

  • Page 143: Appendix B: System Profiles

    B–1 A P P E N D I X System Profiles This appendix contains device and storageset profiles you can use to create your system profiles. It also contains an enclosure template you can use to help keep track of the location of devices and storagesets in your shelves.

  • Page 144: Device Profile

    B–2 Configuration Manual Device Profile Type ___ Platter disk drive ___ Optical disk drive ___ Tape Drive ___ CD-ROM Device Name ______________________________________________________________ Unit Number______________________________________________________________ Device Switches Transportability ___ No (default) ___ Yes Initialize Switches Chunk size Save Configuration Metadata ___ Automatic (default) ___ No (default) ___ Destroy (default) ___ 64 blocks...

  • Page 145: Storageset Profile

    B–3 Storageset Profile Type ___ RAIDset ___ Stripeset ___ Mirrorset ___ Striped Mirrorset Storageset Name ___________________________________________________________ Disk Drives ________________________________________________________________ Unit Number ______________________________________________________________ Partitions Unit # Unit # Unit # Unit # Unit # Unit # Unit # Unit # RAIDset Switches Reconstruction Policy Reduced Membership Replacement Policy...

  • Page 146: Ba370 Rack-Mountable Enclosure Template

    B–4 Configuration Manual BA370 Rack-Mountable Enclosure Template Power Power Supply Supply Power Power Supply Supply Power Power Supply Supply Power Power Supply Supply...

  • Page 147: Glossary

    G–1 Glossary This glossary defines terms pertaining to the HSZ70 array controller. It is not a comprehensive glossary of computer terms. adapter A device that converts the protocol and hardware interface of one bus type into another without changing the function of the bus. array controller See controller.
  • Page 148 G–2 Configuration Manual Cable distribution unit. The power entry device for StorageWorks cabinets. The CDU provides the connections necessary to distribute power to the cabinet shelves and fans. channel Another term for a SCSI bus. See also SCSI. chunk A block of data written by the host. chunk size The number of data blocks, assigned by a system administrator, written to the primary RAIDset or stripeset member before the remaining data...
  • Page 149 G–3 data center cabinet A generic reference to large DIGITAL subsystem cabinets, such as the SW600-series and 800-series cabinets in which StorageWorks components can be mounted. data striping The process of segmenting logically sequential data, such as a single file, so that segments can be written to multiple physical devices (usually disk drives) in a round-robin fashion.
  • Page 150 G–4 Configuration Manual DWZZB A StorageWorks SCSI bus signal converter used to connect a variety of 16-bit single-ended devices to hosts with 16-bit differential SCSI adapters. See also SCSI bus signal converter. DWZZC The 16-bit SCSI table-top SCSI bus signal converter used to extend a differential SCSI bus, or connect a differential SCSI bus to a single ended SCSI bus.
  • Page 151 G–5 FCC Class B This certification label appears on electronic devices that can be used in either a home or a commercial environment within the United States. FD SCSI The fast, narrow, differential SCSI bus with an 8-bit data transfer rate of 10 MB/s.
  • Page 152 G–6 Configuration Manual hot swap A method of device replacement that allows normal I/O activity on a device’s bus to remain active during device removal and insertion. The device being removed or inserted is the only device that cannot perform operations during this process. See also cold swap and warm swap.
  • Page 153 G–7 task’s I/O operations. Each task in the system must establish its own correspondence between logical unit numbers and physical devices. Least recently used. A cache term used to describe the block replacement policy for read cache. maintenance terminal An EIA-423-compatible terminal used with the controller. This terminal is used to identify the controller, enable host paths, enter configuration information, and check the controller’s status.
  • Page 154 G–8 Configuration Manual normalizing Normalizing is a state in which, block-for-block, data written by the host to a mirrorset member is consistent with the data on other normal and normalizing members. The normalizing state exists only after a mirrorset is initialized. Therefore, no customer data is on the mirrorset. normalizing member A mirrorset member whose contents is the same as all other normal and normalizing members for data that has been written since the...
  • Page 155 G–9 partition A logical division of a container, represented to the host as a logical unit. port (1) In general terms, a logical channel in a communications system. (2) The hardware and software used to connect a host controller to a communications bus, such as a SCSI bus or serial bus.
  • Page 156 G–10 Configuration Manual RAID level 1 A RAID storageset of two or more physical disks that maintains a complete and independent copy of the entire virtual disk's data. This type of storageset has the advantage of being highly reliable and extremely tolerant of device failure.
  • Page 157 G–11 member and all of the other members include associated parity information. regeneration (1) The process of calculating missing data from redundant data. (2) The process of recreating a portion of the data from a failing or failed drive using the data and parity information from the other members within the storageset.
  • Page 158 G–12 Configuration Manual SCSI device (1) A host computer adapter, a peripheral controller, or an intelligent peripheral that can be attached to the SCSI bus. (2) Any physical unit that can communicate on a SCSI bus. SCSI device ID number A bit-significant representation of the SCSI address referring to one of the signal lines, numbered 0 through 7 for an 8-bit bus, or 0 through 15 for a 16-bit bus.
  • Page 159 G–13 storage unit The general term that refers to storagesets, single-disk units, and all other storage devices that are installed in your subsystem and accessed by the host. A storage unit can be any entity that is capable of storing data, whether it is a physical device or a group of physical devices.
  • Page 160 G–14 Configuration Manual target (1) A SCSI device that performs an operation requested by an initiator. (2) Designates the target identification (ID) number of the device. target ID number The address a bus initiator uses to connect with a bus target. Each bus target is assigned a unique target address.
  • Page 161 G–15 write-back caching A cache management method used to decrease the subsystem’s response time to write requests by allowing the controller to declare the write operation “complete” as soon as the data reaches its cache memory. The controller performs the slower operation of writing the data to the disk drives at a later time.
  • Page 163 Index memory sizes supported, 1-4 Caution, defined, xiii Abbreviations, xv CFMENU ACCESS_ID, 3-40 adding disk drives, 4-23 Adding disk drives adding disk drives to the spareset, 4-26 as eligible devices, 4-2 configuring storagesets, 4-24 to spareset manually, 4-16 deleting storagesets, 4-25 to spareset with CFMENU, 4-26 guidelines, 4-23 with CFMENU, 4-23...
  • Page 164 Configuration Manual backplane, 1-6 overview, 1-2 device ports, 1-6 reconstruction policy, 3-27 host port, 1-6 replacement policy, 3-27 LEDs, 1-6 reset button, 1-6 program-card slot, 1-6 single configuration, 2-3 reset button, 1-6 summary of features, 1-4 Configured PTLs, 4-22 Conventions Configuring abbreviations, xv controller, 2-9...
  • Page 165 Disk drives configuring a passthrough device, 4-14 adding, 4-2 configuring a RAIDset, 4-8 adding to spareset manually, 4-16 configuring a single-disk unit, 4-12 adding to spareset with CFMENU, 4-26 configuring a striped mirrorset, 4-10 adding with CFMENU, 4-23 configuring a stripeset, 4-4 array, 3-5 configuring a tape drive, 4-13 corresponding storagesets, 3-19...
  • Page 166 Configuration Manual Interconnect supported, 1-4 configuring with CFMENU, 4-24 description, 1-3, 3-9 initialize switches, 4-5 planning, 3-9 JBOD, 3-5 switches, 3-29, 4-4 temporary from CLONE, 5-5 unit switches, 4-5 Largest device supported, 1-5 Moving storagesets, 3-44 LEDs, 1-6 MTBF, See Mean time between failures Local terminal, G-6 Multiple host environment, 3-41 Local-connection port...
  • Page 167 device, 1-4 host, 1-4 Partitioned storageset unit switches, 4-15 PTL addressing convention, 3-20 Partitioning PTL designation disk drives, 4-14 defined, G-9 single-disk units with CFMENU, 4-26 Publications, related, xv storagesets manually, 4-14 storagesets with CFMENU, 4-26 Partitions Quiesce, G-9 defining, 3-24 displaying with CFMENU, 4-23 guidelines, 3-25 planning, 3-24...
  • Page 168 Configuration Manual REDUCED, 3-28 Storageset name, 4-22 redundancy, defined, G-10 Storageset profile, 3-2, B-3 regenerate process, defined, G-11 Storageset type, 4-22 Related publications, xv Storagesets Removing assigning unit numbers, 3-17 disk drives from sparesets, 4-17 attributes, 3-5 storagesets, 4-25 backing up, 5-5 Replacement policy switch, 3-27, 3-29 changing switches, 4-19 Request rate, 3-33...
  • Page 169 unit switches, 4-3 RECONSTRUCT=NORMAL, 3-27 Subsystem REDUCED, 3-28 restarting, 5-13 SAVE_CONFIGURATION, 3-36 saving configuration, 3-36 TRANSFER_RATE_REQUESTED, 3-32 shutting down, 5-12 TRANSPORTABLE, 3-31 SW370 cabinet template, B-4 WRITE_PROTECT, 3-43 Switches WRITEBACK_CACHE, 3-43 ACCESS_ID, 3-40 changing, 3-26 changing for devices, 4-19, 4-20 Tape drives configuring, 4-12 changing for storagesets, 4-19 Tape loaders, configuring, 4-13...
  • Page 170 Configuration Manual partitioned storagesets, 4-15 RAIDsets, 4-8 READ_CACHE, 3-42 striped mirrorsets, 4-9 stripesets, 4-3 WRITE_PROTECT, 3-43 WRITEBACK_CACHE, 3-43 VHDCI cable precautions, xi Warning, defined, xiii Write hole, G-15 Write performance, 3-35 Write protection switch displaying with CFMENU, 4-23 setting, 3-43 WRITE_PROTECT, 3-43 Write-back cache switch displaying with CFMENU, 4-23...

Table of Contents