HSZ80 Array Controller ACS Version 8.3 Configuration and CLI Reference Guide First Edition (December 1998) Part Number EK-HSZ80-RG.
While Compaq Computer Corporation believes the information included in this manual is correct as of the date of publication, it is subject to change without notice. Compaq 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.
JAPAN USA This equipment generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of FCC rules, which are designed to provide reasonable protection against such radio frequency interference. Operation of this equipment in a residential area may cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference.
v About This Guide Getting Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Required Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi Chapter 3 Creating Storagesets Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2 Planning and Configuring Storagesets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–4 Creating a Storageset and Device Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–5 Determining Storage Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii Chapter 5 CLI Commands CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–2 ADD DISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–7 ADD MIRRORSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–11 ADD PASSTHROUGH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–16 ADD RAIDSET.
viii MIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–70 POWEROFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–74 REDUCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–77 RENAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix Appendix A System Profiles Device Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–2 Storageset Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–3 Enclosure Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–4 Appendix B Controller Specifications Physical and Electrical Specifications for the Controller . . . . . . . . . . .
xi Figures Basic Building Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3 Bridging the Gap Between the Host and Its Storage Subsystem . . . . . . . . . . . . . . 1–7 HSZ80 Array Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9 Parts Used in Configuring the HSZ80 Array Controller . . . . . . . . . . . . . . . . . . . 1–10 Optional Maintenance Port Cable for a Terminal Connection . . . . . . . . .
xii Storageset Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–35 PTL Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–37 PTL Addressing in an Extended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 3–38 Locating Devices using PTLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–39 Partitioning a Single-Disk Unit . . . . . . . . . . . . .
xiii Tables Basic Building Blocks List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4 Summary of Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5 HSZ80 Array Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9 Description of Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiv Optimum Operating Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . .B–3 Maximum Operating Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . B–4 Maximum Nonoperating Environmental Specifications . . . . . . . . . . . . . . . . . . . .
xv About This Guide This book describes the features of the HSZ80 Array Controller, configuration procedures for the controller and storagesets running Array Controller Software (ACS) 8.3Z, and the CLI commands used in configuring. 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.
xvi About This Guide 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.
xvii VHDCI Cable Precautions All of the cables to the controller, cache module, and external cache battery use veryhigh-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. ■ Mate the connectors by hand, then tighten the retaining screws to 1.
xviii About This Guide Conventions This book uses the following typographical conventions and special notices to help you find what you’re looking for. Typographical Conventions Convention ALLCAPS Meaning Command syntax that must be entered exactly as shown and for commands discussed within text, for example: SET FAILOVER COPY=OTHER_CONTROLLER “Use the SHOW SPARESET command to show the contents of the spareset.” Monospaced Screen display.
xix 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 observe the precautions in the text.
xx About This Guide Required Tools You’ll need the following tools to service the controller, cache module, external cache battery (ECB), the Power Verification and Addressing (PVA) module and the I/O module: ■ A flathead screwdriver for loosening and tightening the I/O module retaining screws. ■ A small phillips screwdriver for loosening and tightening the GLM access door screws. ■ An antistatic wrist strap. ■ An antistatic mat on which to place modules during servicing.
xxi Related Publications The following table lists some of the Compaq StorageWorks documents related to the use of the controller, cache module, external cache battery, graphical user interface, and the subsystem. Document Title BA370 Enclosure Rack Template (Compaq 42U Rack) Command Console Version 2.
xxii About This Guide Document Title RA8000/ESA12000 HSZ80 ACS V8.3 for DIGITAL UNIX Quick Setup Guide RA8000/ESA12000 HSZ80 ACS V8.3 for IBM-AIX Installation Reference Manual RA8000/ESA12000 HSZ80 ACS V8.3 for IBM-AIX Quick Setup Guide RA8000/ESA12000 HSZ80 ACS V8.3 for OpenVMS Installation Reference Manual RA8000/ESA12000 HSZ80 ACS V8.
1–1 Chapter 1 General Description This chapter illustrates and describes in general terms your subsystem and its major components: the HSZ80 Array Controller, its cache module, and its external cache battery (ECB). Compaq HSZ80 Array Controller ACS Version 8.
1–2 General Description Typical Installation Figure shows the major components, or basic building blocks, of the storage subsystem that is comprised of the following: ■ One BA370 rack-mountable enclosure. ■ Two controllers, each supported by a cache module. ■ Two External Cache Batteries (ECBs) in one Storage Building Block (SBB), which provide backup power to the cache modules during a primary power failure.
1–3 1 16 2 15 13 14 3 12 2x 4 11 10 9 2x 5 8 2x 6 7 CXO6742A Figure 1–1. Basic Building Block Compaq HSZ80 Array Controller ACS Version 8.
1–4 General Description Table 1–1 Basic Building Blocks List Item Description 1 BA370 rack-mountable enclosure 2 Cooling fan 3 Power cable kit 4 I/O module 5 SCSI hub, 3 port 6 SCSI hub, 5 port 7 SCSI hub, 9 port, upgrade 8 Cache module 9 HSZ80 controller 10 PVA module 11 EMU 12 AC input module 13 180-watt power supply 14 Disk drive, 4 GB, 7200 Disk drive, 9 GB, 7200 Disk drive, 18 GB, 7200 Disk drive, 9 GB, 10K Disk drive, 18 GB, 10K 15 Power cable 16 ECB, dual (shown) EC
1–5 Summary of HSZ80 Features Table 1–2 summarizes the features of the controller: Table 1–2 Summary of Controller Features Feature Supported Topology Dual host port Ultra SCSI Host protocol SCSI-2, Limited SCSI-3 Host bus interconnect Wide Ultra SCSI, Differential Number of host ports 2 on Wide Ultra SCSI, Differential Device protocol SCSI-2 Device bus interconnect Wide Ultra SCSI, Single-ended Number of SCSI device ports (or I/O modules) 6 Wide Ultra SCSI, Single-ended Number of SCSI dev
1–6 General Description Table 1–2 Summary of Controller Features (Continued) Feature Supported Maximum number of members in a stripeset 24 Maximum number of physical devices in a striped mirrorset 48 Maximum host port transfer speed 20 MHz Largest device, storageset, or unit size 512 GB
1–7 The HSZ80 Array Controller Your controller is the intelligent bridge between your host and the devices in your subsystem. Storage subsystem Host Controller CXO5505A Figure 1–2. Bridging the Gap Between the Host and Its Storage Subsystem The controller shown in Figure 1–2 is an integral part of any storage subsystem because it provides a host with high-performance and high-availability access to storage devices. See the HSZ80 Array Controller ACS Version 8.
1–8 General Description From the host’s perspective, the controller is simply another 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. From the subsystem’s perspective, the controller receives the I/O requests and directs them to the devices in the subsystem.
1–9 1 2 3 4 5 6 1 2 3 4 5 6 7 8 CXO6284B Figure 1–3. HSZ80 Array Controller Table 1–3 HSZ80 Array Controller Item Description ➀ Backplane connector ➁ Host port 1 ➂ Host port 2 ➃ Program card slot ➄ Program card ejection button ➅ Release lever ➆ Maintenance port ➇ Operator Control panel Compaq HSZ80 Array Controller ACS Version 8.
1–10 General Description 2 1 3 4 1 2 3 4 5 6 5 6 7 10 8 9 CXO6492B Figure 1–4.
1–11 Table 1–4 Description of Parts (Continued) Item Description ➆ Ferrite bead ➇ Terminator ➈ Jumper cable ➉ Maintenance port cable Compaq HSZ80 Array Controller ACS Version 8.
1–12 General Description 1 2 3 4 5 CXO6505B Figure 1–5. Optional Maintenance Port Cable for a Terminal Connection Table 1–5 Parts of the Optional Maintenance Port Cable Item Description ➀ Cable assembly ➁ Ferrite bead ➂ RJ-11 Adapter ➃ RJ-11 Extension Cable ➄ PC Serial Port Adapter Each controller is supported by its own cache module. Figure 1–6 shows which cache module supports which controller in a dual-redundant controller configuration in a BA370 rack-mountable enclosure.
1–13 EMU PVA Controller A Controller B Cache module A Cache module B CXO6283A Figure 1–6. Location of Controllers and Cache Modules IMPORTANT: Compaq recommends that you use the slots for controller A and cache module A for single controller configurations. Slot A responds to SCSI target ID number 7 on the device buses and slot B responds to SCSI target ID number 6 on the device buses.
1–14 General Description Reset button/ LED 1 Port button/ LED 2 3 4 5 6 CXO6216A Figure 1–7. HSZ80 Controller Operator Control Panel (OCP) See Figure 1–3 on page 1–9 for the location of the OCP on the HSZ80 Array Controller. Under normal circumstances, you will not need to remove the controller from its enclosure. For this reason, the components that you will use most often are conveniently located on the front panel.
1–15 Utilities and Exercisers The controller’s software includes the following utilities and exercisers to assist in troubleshooting and maintaining the controller and the other modules that support its operation. For more details on each of the utilities and exercisers, see the HSZ80 Array Controller ACS Version 8.3 Maintenance and Service Guide. Fault Management Utility The Fault Management Utility (FMU) provides a limited interface to the controller’s fault management system.
1–16 General Description 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 SCSI–2 disk drives attached to it. DILX generates intense read and write loads to the disk drive while monitoring the drive’s performance and status. Configuration Utility Use the configuration (CONFIG) utility to add one or more storage devices to the subsystem.
1–17 Field Replacement Utility Use the field replacement utility (FRUTIL) to replace a failed controller (in a dualredundant configuration) without shutting down the subsystem.You can also use this menu-driven utility to replace cache modules, external cache batteries, and the PVA module. Change Volume Serial Number Utility Only Compaq authorized service personnel may use this utility.
1–18 General Description Cache Module Each controller requires a companion cache module as shown in Figure 1–8. Table 1–7 lists the descriptions and part numbers of the cache module. Figure 1–6 on page 1–13 shows the location of a controller’s companion cache module. The cache module, which contains up to 512 MB of memory, increases the subsystem’s I/O performance by providing read, read-ahead, write-through, and write-back caching.
1–19 5 4 1 ~ 2 3 CXO6306B Figure 1–8. Cache Module Table 1–7 Location of Cache Module Parts Item Description ➀ Cache memory power LED ➁ ECB Y cable ➂ Release lever ➃ Backplane connector ➄ DIMM Compaq HSZ80 Array Controller ACS Version 8.
1–20 General Description Caching Techniques The cache module supports the following caching techniques to increase the subsystem’s read and write performance: ■ Read caching ■ Read-ahead caching ■ Write-through caching ■ Write-back caching Read Caching When the controller receives a read request from the host, it reads the data from the disk drives, delivers it to the host, and also stores the data in its cache module. This process is called read caching.
1–21 The controller then anticipates subsequent read requests and begins to prefetch the next blocks of data from the disks as it sends the requested read data to the host. This is a parallel action. The controller notifies the host of the read completion, and subsequent sequential read requests are satisfied through the cache memory. By default, read-ahead caching is enabled for all disk units.
1–22 General Description Fault-Tolerance for Write-Back Caching The cache module supports nonvolatile memory and dynamic cache policies to protect the availability of its unwritten (write-back) data. Nonvolatile Memory Except for disaster-tolerant supported mirrorsets, the controller can provide writeback caching for storage units as long as the controller’s cache memory is nonvolatile.
1–23 Table 1–9 shows the cache policies resulting from a full or partial failure of cache module A’s ECB in a dual-redundant controller configuration. When cache module A is at least 50% charged, the ECB is still good and is charging. When it is less than 50% charged, the ECB is low, but still charging. The consequences shown are the opposite for a failure of cache module B’s ECB.
1–24 General Description Table 1–8 Cache Policies and Cache Module Status (Continued) Cache Module Status Cache A DIMM or cache memory controller chip failure Cache B Good Cache Policy Unmirrored Cache Mirrored Cache Data integrity: Write-back data that was not written to media when failure occurred was not recovered. Data integrity: Controller A recovers all of its write-back data from the mirrored copy on cache B.
1–25 Table 1–8 Cache Policies and Cache Module Status (Continued) Cache Module Status Cache A Cache Board Failure Cache B Good Cache Policy Unmirrored Cache Same as for DIMM failure. Mirrored Cache Data integrity: Controller A recovers all of its write-back data from the mirrored copy on cache B. Cache policy: Both controllers support write-through caching only. Controller B cannot execute mirrored writes because cache module A cannot mirror controller B’s unwritten data. Failover: No.
1–26 General Description Table 1–9 Resulting Cache Policies and ECB Status (Continued) Cache Module Status Cache A Less than 50% charged Cache B At least 50% charged Cache Policy Unmirrored Cache Mirrored Cache Data loss: No. Data loss: No. Cache policy: Controller A supports write-through caching only; controller B supports write-back caching. Cache policy: Both controllers continue to support write-back caching. Failover: In transparent failover, all units failover to controller B.
1–27 Table 1–9 Resulting Cache Policies and ECB Status (Continued) Cache Module Status Cache A Failed Cache B At least 50% charged Cache Policy Unmirrored Cache Mirrored Cache Data loss: No. Data loss: No. Cache policy: Controller A supports write-through caching only; controller B supports write-back caching. Cache policy: Both controllers continue to support write-back caching. Failover: No. Failover: In transparent failover, all units failover to controller B and operate normally.
1–28 General Description Table 1–9 Resulting Cache Policies and ECB Status (Continued) Cache Module Status Cache A Failed Cache B Less than 50% charged Cache Policy Unmirrored Cache Mirrored Cache Data loss: No. Data loss: No. Cache policy: Both controllers support write-through caching only. Cache policy: Both controllers support write-through caching only. Failover: In transparent failover, all units failover to controller B and operate normally. Failover: No.
1–29 External Cache Battery To preserve the write-back cache data in the event of a primary power failure, a cache module must be connected to an ECB or a UPS. Compaq supplies two versions of ECBs: a single-battery ECB for single controller configurations, and a dual-battery ECB for dual-redundant controller configurations, which is shown in Figure 1–9. When the batteries are fully charged, an ECB can preserve 512 MB of cache memory for 24 hours.
General Description 1 SH US STAT OFF UT 2 HE CAC ER W PO 1–30 HE CAC ER W PO US STAT OFF UT SH 4 3 ~ CXO6305B Figure 1–9.
1–31 Charging Diagnostics Whenever you restart the controller, its diagnostic routines automatically check the charge in the ECB’s batteries. If the batteries are fully charged, the controller reports them as fully charged and rechecks them every 24 hours. If the batteries are charging, the controller rechecks them every 4 minutes. Batteries are reported as being either above or below 50 percent in capacity. Batteries below 50 percent in capacity are also referred to as being low.
2–1 Chapter 2 Configuring an HSZ80 Array Controller This chapter explains how to configure an HSZ80 Array Controller and the modules that support its operation in a StorageWorks subsystem. Compaq HSZ80 Array Controller ACS Version 8.
2–2 Configuring an HSZ80 Array Controller Introduction Use the Quick Setup Guide that came with your subsystem to unpack and set up your subsystem prior to configuring your controller. 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.
2–3 Configuring an HSZ80 Array Controller You can use this procedure to configure your controller in one of three configurations: 1) single controller, 2) dual controllers in transparent failover mode, or 3) dual controllers in multiple-bus failover (host-assisted) mode. When you are done configuring the controller, you can then add devices, plan storagesets, and configure storagesets. These tasks can be performed either with SWCC or using CLI commands from a PC or terminal.
2–4 Configuring an HSZ80 Array Controller ■ CLI Commands—A few commands can be used while configuring the controller: ❏ CLEAR_ERRORS CLI—Clears all error messages so you can type without the messages being repeated. Make sure you read each error message before deleting it. ❏ SHOW THIS_CONTROLLER FULL and SHOW OTHER_CONTROLLER FULL—Lists the full information about the controller.
2–5 Configuring a Single Controller 1 2 3 1 2 3 4 5 6 4 5 or 4 6 CXO6285B Figure 2–1. Cabling for a Single-Controller Configuration Table 2–1 Location of Parts for a Single Controller Configuration Item Description ➀ Host port 1 ➁ Host port 2 ➂ Trilink connector ➃ Host bus cable ➄ Ferrite bead ➅ Terminator Compaq HSZ80 Array Controller ACS Version 8.
2–6 Configuring an HSZ80 Array Controller Follow these steps to configure a controller: NOTE: This procedure has been written for first-time configuring. However, you can adapt the procedure when you reconfigure the controllers. For replacing and upgrading the controllers, see the HSZ80 Array Controller ACS Version 8.3 Maintenance and Service Guide. 1. Use the power-verification and addressing (PVA) module ID switch to set the SCSI ID number for the BA370 rack-mountable enclosure.
2–7 6. Set the host function mode for the controller using the target ID numbers set in step 5. Use the following command: NOTE: The default host function mode defaults to Host Mode A. The HOST_FUNCTION switch changes the host function mode to a different mode. SET THIS_CONTROLLER HOST_FUNCTION= (ID, MODE) To change the host function mode, see “SET controller,” page 5–91 for information on the HOST_FUNCTION switch. 7.
2–8 Configuring an HSZ80 Array Controller 10. Enter any other optional CLI commands for your configuration. See “Optional Steps,” page 2–22 and Chapter 5, “CLI Commands.” 11. Display details about the controller you configured. Use the following command: SHOW THIS_CONTROLLER FULL See “SHOW” in Chapter 5, “CLI Commands.” IMPORTANT: If you are using a PC or terminal with the maintenance port cable, you must connect the SCSI bus cables in the desired configuration.
2–9 Connecting a Single Controller to the Host Follow these steps and Figure 2–1 to connect a single, nonredundant controller to the host: 1. Configure the controller. See “Configuring a Single Controller,” page 2–5. 2. Ensure the host and adapter are also configured. See the host user’s guide for details. 3. Connect a trilink to the controller going into host Port 1: 4. 5. a. Connect the host bus cable onto one end of the trilink connector. b.
2–10 Configuring an HSZ80 Array Controller Configuring Dual-Redundant Controllers in Transparent Failover Mode 1 2 3 1 1 2 2 3 3 4 4 5 5 4 6 5 6 7 3 4 or 6 CXO6287B Figure 2–2.
2–11 Table 2–2 Location of Parts for Transparent Failover Item Description ➀ Host port 1 ➁ Host port 2 ➂ Trilink connector ➃ Host bus cable ➄ Ferrite bead ➅ Terminator ➆ Jumper cable Follow these steps to configure a controller: NOTE: This procedure has been written for first-time configuring. However, you can adapt the procedure when you reconfigure the controllers. For replacing and upgrading the controllers, see the HSZ80 Array Controller ACS Version 8.3 Maintenance and Service Guide. 1.
2–12 Configuring an HSZ80 Array Controller 5. Put this controller into transparent failover mode. Use the following command: CAUTION: Issuing the SET FAILOVER COPY command will overwrite data on the companion controller. If you are reconfiguring the controllers, see “CONFIGURATION RESET” in Chapter 5, “CLI Commands,” before proceeding and for more information. SET FAILOVER COPY = THIS_CONTROLLER The other controller inherits this controller’s configuration, then restarts.
2–13 8. If you are configuring controllers in transparent failover mode, prefer some or all SCSI target ID numbers to the controllers. Use the following command: SET THIS_CONTROLLER PORT_1_PREFERRED_ID = (n, n) or SET THIS_CONTROLLER PORT_2_PREFERRED_ID = (n,n) where n,n is a subset of the target ID numbers you declared in step 5. See “Using Preferred ID Numbers,” page 2–35, for details about preferred SCSI target ID numbers. 9.
2–14 Configuring an HSZ80 Array Controller 11. Set the time on the controller, which provides a baseline for replacing the external battery, using the following command: SET THIS_CONTROLLER TIME=DD-MMM-YYYY:HH:MM:SS NOTE: All values are numbers, except for MMM, which uses the first three letters of the month. When setting hours, minutes, and seconds—HH, MM, and SS—you must use 24-hour time. 12. Set up the battery discharge timer: a.
2–15 Connecting in Transparent Failover Mode to the Host Use the following steps and Figure 2–2 to connect a pair of dual-redundant controllers to the host: 1. Configure both controllers. See “Configuring Dual-Redundant Controllers in Transparent Failover Mode,” page 2–10. 2. Ensure the host and adapter are also configured. See the host user’s guide for details. 3. Connect two trilink connectors between both controllers going into host Port 1 with a jumper cable: 4. a.
2–16 Configuring an HSZ80 Array Controller Configuring Dual-Redundant Controllers in Multiple-Bus Failover Mode 1 2 4 3 1 1 2 2 3 3 4 4 5 5 5 6 6 4 3 or 4 5 4 6 or 6 CXO6286B Figure 2–3.
2–17 Table 2–3 Location of Parts for Multiple-Bus Failover Item Description ➀ Host port 1 ➁ Host port 2 ➂ Trilink connector ➃ Host bus cable ➄ Ferrite bead ➅ Terminator Follow these steps to configure a controller: NOTE: This procedure has been written for first-time configuring. However, you can adapt the procedure when you reconfigure the controllers. For replacing and upgrading the controllers, see the HSZ80 Array Controller ACS Version 8.3 Maintenance and Service Guide. 1.
2–18 Configuring an HSZ80 Array Controller 5. Put this controller in multiple-bus failover mode, using the following command: CAUTION: Issuing the SET MULTIBUS_FAILOVER COPY command will overwrite data on the companion controller. If you are reconfiguring the controllers, see “CONFIGURATION RESET” in Chapter 5, “CLI Commands,” before proceeding and for more information. SET MULTIBUS_FAILOVER COPY = THIS_CONTROLLER The other controller inherits this controller’s configuration, then restarts.
2–19 8. Set the host function mode for the controller using the target ID numbers set in step 7. Use the following command: NOTE: The default host function mode defaults to Host Mode A. The HOST_FUNCTION switch changes the host function mode to a different mode. SET THIS_CONTROLLER HOST_FUNCTION= (ID, MODE) or SET OTHER_CONTROLLER HOST_FUNCTION= (ID, MODE) To change the host function mode, see “SET controller,” page 5–91 for information on the HOST_FUNCTION switch. 9.
2–20 Configuring an HSZ80 Array Controller 11. Set up the battery discharge timer: a. Start Frutil using the following command: RUN FRUTIL Frutil displays the following: Do you intend to replace this controller’s cache battery? Y/N b. Enter Y(es). Frutil displays a three-step procedure and prompts you to press return. c. Press return. 12. Enter any other optional CLI commands for your configuration. See the following section, “Optional Steps,” and Chapter 5, “CLI Commands.” 13.
2–21 Connecting in Multiple-Bus Failover Mode to the Host Use the following steps and Figure 2–3 to connect a pair of multiple-bus failover, dual-redundant controllers to the host: 1. Configure both controllers. See “Configuring Dual-Redundant Controllers in Multiple-Bus Failover Mode,” page 2–16. 2. Ensure the host and adapter are also configured. See the host user’s guide for details. 3. Connect a trilink connector on host Port 1 or host Port 2 for one controller: 4. 5. a.
2–22 Configuring an HSZ80 Array Controller 6. Repeat steps 3, 4, and 5 for connecting a third and a fourth host bus. IMPORTANT: The HSZ80 Array Controller has dual-host ports, Port 1 and Port 2, which may be configured at the same time. The configuration in Figure 2–3 shows a two-bus connection going into host Port 1. However, you may also configure host Port 2 the same way, depending on your system requirements.
2–23 Set the maximum data-transfer rate Use the following command: SET THIS_CONTROLLER PORT_1_TRANSFER_RATE_REQUESTED = speed or SET THIS_CONTROLLER PORT_2_TRANSFER_RATE_REQUESTED = speed If you are configuring dual-redundant controllers, also set the transfer rate for the other controller. However, if you are running more than one HSZ80 SCSI host port on the same bus, you must set their transfer rates to be identical.
2–24 Configuring an HSZ80 Array Controller UPS Support NOTE: By default, the controller expects to use an external cache battery (ECB) as backup power to the cache module. You can instead choose to use an uninterruptable power supply (UPS) to provide backup power in the event of a primary power failure. Use the following command: SET THIS_CONTROLLER CACHE_UPS If you are configuring dual-redundant controllers, also indicate that the other controller’s power is supported by a UPS.
2–25 Setting the PVA Module ID Switch The Power, Verification, and Addressing (PVA) module provides unique addresses to extended subsystems. Each BA370 rack-mountable enclosure in an extended subsystem must have its own PVA ID. Use PVA ID 0 for the enclosure that contains the controllers. Use PVA IDs 2 and 3 for the additional enclosures. Figure 2–4 illustrates the PVA settings in an extended subsystem. See the documentation that accompanied your enclosure for more details about the PVA and its settings.
2–26 Configuring an HSZ80 Array Controller Establishing a Local Connection to the Controller You can communicate with a controller locally or remotely. Use a local connection to configure the controller for the first time. Use a remote connection to your host system for all subsequent configuration tasks. See the Quick Setup Guide that came with your platform kit for details.
2–27 1 2 3 4 5 6 Maintenance port cable Maintenance port CXO6484A Figure 2–5. PC/Terminal to Maintenance Port Connection CAUTION: The maintenance port described in this book generates, uses, and can radiate radio-frequency energy through cables that are connected to it. This energy may interfere with radio and television reception. Disconnect all maintenance port cables when you are not communicating with the controller.
2–28 Configuring an HSZ80 Array Controller b. If you are using a terminal instead of a PC, you can order a cable from the local field service office as shown in figure 1-5. 2. Turn on the PC or terminal. 3. Configure the PC or terminal for 9600 baud, 8 data bits, 1 stop bit, and no parity. The default baud rate for the HSZ80 Array Controller is 9600, which makes communication between the two compatible. 4. Press the Enter or Return key.
2–29 Selecting a Failover Mode In selecting a failover mode, you have two choices: transparent failover or multiplebus failover. If you want the failover to occur without any intervention from the host, then transparent failover is best suited. The devices attached to the failed controller fail over to the surviving controller. With multiple-bus failover, the host intervenes during failover and sends commands to the companion controller.
2–30 Configuring an HSZ80 Array Controller ■ For better subsystem performance, balance your assignment of target ID numbers across your dual-redundant pair of controllers. 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. For example, in an 18-device subsystem, place 3 devices on each of the 6 ports, rather than placing 6 devices on each of 3 ports.
2–31 Enabling Mirrored Write-Back Cache Before configuring dual-redundant controllers and enabling mirroring, ensure the following conditions are met: ■ Both controllers support the same size cache: 64 MB, 128 MB, 256 MB, or 512 MB. ■ Diagnostics indicates that both caches are good. ■ If you have not enabled the CACHE_UPS switch, then both caches have a battery present. A battery does not have to be present for either cache if you enable the CACHE_UPS switch.
2–32 Configuring an HSZ80 Array Controller Fault-Tolerance The cache module supports the following features to protect the availability of its unwritten (write-back) data: ■ Nonvolatile memory (required for write-back caching) ■ Dynamic caching techniques (automatic) For details about these features, see “Fault-Tolerance for Write-Back Caching,” page 1–22.
2–33 Setting SCSI Target ID Numbers In a subsystem, every SCSI device is assigned its own SCSI ID number. Setting an ID number, though, really depends on which SCSI bus you are talking about—the host SCSI bus or the controller device bus, which are both shown in Figure 2–7. Controller device bus Host Controller A Controller B Host SCSI bus CXO6320A Figure 2–7.
2–34 Configuring an HSZ80 Array Controller You can view IDs on this controller with the following command: SHOW THIS_CONTROLLER FULL You can view IDs on the other controller with the following command: SHOW OTHER_CONTROLLER FULL The valid target ID numbers are 0–15, with one ID reserved for each host controller on the host bus. When both ports are in use, the 16 target ID numbers are shared across ports. Once a target ID has been set on one port, that same target may not be used on the other port.
2–35 Using Preferred ID Numbers Use preferred SCSI target ID numbers to balance the I/O load of storage units among controllers and thereby improve the throughput for the dual-redundant pair of controllers. You can specify a total of 15 SCSI target ID numbers across both host ports or you can specify 15 SCSI target ID numbers to either Port 1 or Port 2. Use the ID numbers you defined with the SET THIS_CONTROLLER PORT_1_ID (or PORT_2_ID) command.
3–1 Chapter 3 Creating Storagesets This chapter provides information to help you create storagesets for your subsystem. The procedure in this chapter takes you through the planning steps and procedures for creating storagesets. Compaq HSZ80 Array Controller ACS Version 8.
3–2 Creating Storagesets Introduction Storagesets are implementations of RAID technology, also known as a Redundant Array of Independent Disks. Every storageset shares one important feature: each one looks like a single storage unit to the host, regardless of the number of drives it uses. You can 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 3–1.
3–3 Unit Unit Mirrorset Unit Stripeset Partitioned storageset RAIDset Unit Striped mirrorset Disk drives Unit Partitioned disk drive Unit CXO5368B Figure 3–1. Units Created from Storagesets, Partitions, and Drives Table 3–1 Controller Limitations for RAIDsets RAIDset Type Limit Total number of RAID5 20 Total number of RAID5 + RAID1 30 Total number of RAID5 + RAID1 + RAID0 45 Compaq HSZ80 Array Controller ACS Version 8.
3–4 Creating Storagesets Planning and Configuring Storagesets Use this procedure to plan and configure the storagesets for your subsystem. Use the references in each step to locate details about specific commands and concepts. 1. Create a storageset and device profile. See “Creating a Storageset and Device Profile,” page 3–5 for suggestions about creating a profile. 2. Determine your storage requirements. Use the questions in “Determining Storage Requirements,” page 3–7 to help you. 3.
3–5 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 helps you to make informed decisions about the switches that you can enable for each storageset or storage device that you configure in your subsystem. Familiarize yourself with the kinds of information contained in a storageset profile, as shown in Figure 3–3.
3–6 Creating Storagesets Type of Storageset ___ Mirrorset ✔ RAIDset ___ Stripeset Storageset Name.........accept default values Disk Drives...................DISK10300, DISK20300, DISK30300 Unit Number.................
3–7 Determining Storage Requirements Start the planning process by determining your storage requirements.
3–8 Creating Storagesets 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 technology. Consequently, they all share one important feature: each storageset, whether it contains two disk drives or ten, looks like one large, virtual disk drive to the host.
3–9 Using Stripesets to Increase I/O Performance Stripesets enhance I/O performance by spreading the data across multiple disk drives. Large I/O requests are 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 large I/O request or handle several I/O requests simultaneously.
3–10 Creating Storagesets A major benefit of striping is that it balances the I/O load across all of the disk drives in the storageset. This can increase the subsystem’s performance by eliminating the hot spots, or high localities of reference, that occur when frequently accessed data becomes concentrated on a single disk drive.
3–11 For this reason, you should avoid using a stripeset to store critical data. Stripesets are more suitable for storing data that can be reproduced easily or whose loss does not prevent the system from supporting its critical mission. ■ Evenly distribute the members across the device ports to balance load and provide multiple paths as shown in the Figure 3–4. 1 Device ports 2 3 4 5 6 Backplane 3 4 0 3 0 0 2 3 0 2 0 0 2 0 1 0 0 1 0 1 0 0 0 0 1 2 3 4 5 6 CXO6235A Figure 3–4.
3–12 Creating Storagesets ❏ ❏ Storing program image libraries or run-time libraries for rapid loading Storing large tables or other structures of read-only data for rapid application access ❏ Collecting data from external sources at very high data transfer rates ■ 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 sequen
3–13 Disk 10100 Disk 10000 A A' Disk 20100 Disk 20000 B B' Disk 30100 Disk 30000 C C' Mirror drives contain copy of data CXO5511A Figure 3–5. Mirrorsets Maintain Two Copies of the Same Data Considerations for Planning a Mirrorset Keep these points in mind as you plan your mirrorsets: ■ A controller can support up to 30 storagesets, consisting of mirrorsets and RAIDsets. Mirrorsets that are members of a stripeset count against this limitation (see Table 3–1).
3–14 Creating Storagesets ■ If you are 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–6. The first member of a mirrorset is the first disk drive you add. When a controller receives a request to read data from a mirrorset, it typically accesses the first member of the mirrorset. Read access depends upon the read source switches (see “Read Source,” page 3–46).
3–15 ■ A storageset should only contain disk drives of the same capacity. The controller limits the capacity of each member to the capacity of the smallest member in the storageset when the storagest is initialized (the base member size). Thus, if you combine 9 GB disk drives with 4 GB disk drives in the same storageset, the 4-GB disk drive will be the base member size and you will waste 5 GB of capacity on each 9-GB member.
3–16 Creating Storagesets For example, in a three-member RAIDset that contains disk drives 10000, 20000, and 30000, the first chunk of an I/O request is written to 10000, the second to 20000, then parity is calculated and written to 30000; the third chunk is written to 30000, the fourth to 10000, and so on until all of the data is saved. The relationship between the chunk size and the average request size determines if striping maximizes the request rate or the data-transfer rate.
3–17 ■ Reporting methods and size limitations prevent certain operating systems from working with large RAIDsets. See the HSZ80 Array Controller ACS Version 8.3 Release Notes or the Quick Setup Guide that came with your platform kit for details about these restrictions. ■ A cache module is required for RAIDsets, but write-back cache need not be enabled for the RAIDset to function properly. ■ Both cache modules must be the same size.
3–18 Creating Storagesets 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 (see Figure 3–8).
3–19 Considerations for Planning a Striped Mirrorset Plan the mirrorset members, then plan the stripeset that will contain them. Review the recommendations in “Considerations for Planning a Stripeset,” page 3–10, and “Considerations for Planning a Mirrorset,” page 3–13.
3–20 Creating Storagesets 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. When you are cloning a mirrorset, CLONE does not need to create a temporary mirrorset.
3–21 Unit Unit Temporary mirrorset Disk10300 Disk10300 New member Unit Temporary mirrorset Unit Copy Disk10300 Disk10300 New member Clone Unit Clone of Disk10300 CXO5510A Figure 3–9. CLONE Steps for Duplicating Unit Members Use the following steps to clone a single-disk unit, stripeset, or mirrorset: 1. Establish a connection to the controller that accesses the unit you want to clone. Compaq HSZ80 Array Controller ACS Version 8.
3–22 Creating Storagesets 2. Start CLONE using the following syntax: RUN CLONE 3. When prompted, enter the unit number of the unit you want to clone. 4. When prompted, enter a unit number for the clone unit that CLONE will create. 5. When prompted, indicate how you would like the clone unit to be brought online: either automatically or only after your approval. 6. When prompted, enter the disk drives you want to use for the clone units. 7. Back up the clone unit.
3–23 CLONE WILL CREATE A NEW UNIT WHICH IS A COPY OF UNIT 204. Enter the unit number which you want assigned to the new unit ? 205 THE NEW UNIT MAY BE ADDED USING ONE OF THE FOLLOWING METHODS: 1. CLONE WILL PAUSE AFTER ALL MEMBERS HAVE BEEN COPIED. THE USER MUST THEN PRESS RETURN TO CAUSE THE NEW UNIT TO BE ADDED. 2. AFTER ALL MEMBERS HAVE BEEN COPIED, THE UNIT WILL BE ADDED AUTOMATICALLY.
3–24 Creating Storagesets 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... . . .
3–25 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. See “Considerations for Saving the Configuration,” page 3–55, and “Saving Configuration Information in Dual-Redundant Controller Configurations,” page 3–56, for more information.
3–26 Creating Storagesets Saving Subsystem Configuration Information to Multiple Disks You can save your subsystem configuration information to as many individual disks as you would like, but you must initialize each using the SAVE_CONFIGURATION switch. Use the following syntax for each: INITIALIZE DISKnnnn SAVE_CONFIGURATION Saving Subsystem Configuration Information to a Storageset You can save your subsystem configuration information to a storageset.
3–27 Displaying the Status of the Save Configuration Feature You can use the SHOW THIS_CONTROLLER FULL command to find out if the save configuration feature is active and which devices are being used to store the configuration. The display includes a line that indicates status and how many devices have copies of the configuration, as shown in the following example.
3–28 Creating Storagesets Cache: 128 MEGABYTE WRITE CACHE, VERSION UNKNOWN CACHE IS GOOD UNFLUSHED DATA IN CACHE CACHE_FLUSH_TIMER = DEFAULT (10 SECONDS) Mirrored Cache: NOT ENABLED Battery: FULLY CHARGED EXPIRES: 08-MAY-2000 NOCACHE_UPS Extended information: TERMINAL SPEED 19200 BAUD, EIGHT BIT, NO PARITY, 1 STOP BIT OPERATION CONTROL: 00000000 SECURITY STATE CODE: 36415 CONFIGURATION BACKUP ENABLED ON 2 DEVICES The following example shows sample devices with the SAVE_CONFIGURATION switch enabled: $
3–29 NOTRANSPORTABLE TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 10.00 MHZ negotiated) LOCAL Size: 4108970 blocks Configuration being backed up on this container Compaq HSZ80 Array Controller ACS Version 8.
3–30 Creating Storagesets Node IDs A node ID is a unique 64-bit number assigned to a subsystem by the Institute of Electrical and Electronics Engineers (IEEE) and set by Compaq manufacturing prior to shipping. The node ID assigned to a subsystem never changes. Each subsystem’s node ID ends in zero, for example, 5000-1FE1-FF0C-EE00. The controller port IDs are derived from the node ID.
3–31 CAUTION: Never set two subsystems to the same node ID, or data corruption will occur. Each subsystem has its own unique node ID. This name is printed on the sticker affixed to the horizontal top edge of the Controller Card Cage above the EMU/PVA into which your controller is inserted. If you attempt to set the subsystem node ID to a name other than the one that came with the subsystem, the data on the subsystem will not be accessible. Compaq HSZ80 Array Controller ACS Version 8.
3–32 Creating Storagesets Assigning Unit Numbers for Host Access to Storagesets The HSZ80 controller supports up to 15 SCSI target IDs, each of which can present up to 32 logical unit numbers (LUNs) to a host, depending on the requirements of your operating system. However, a maximum number of 128 storage units can be presented to a host by a controller or a dual-redundant pair of controllers.
3–33 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–3 shows additional unit numbering examples. Table 3–3 Unit Numbering Examples Unit Number D401 D1207 D5 Device Type Disk Disk Disk Target ID Number 4 12 0 LUN 1 7 5 NOTE: The host communicates with a logical unit based on its LUN address.
3–34 Creating Storagesets 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–10. This storageset map is for a subsystem that contains two RAIDsets, two mirrorsets, and three disk drives in the spareset. Each enclosure also has redundant power supplies.
3–35 Figure 3–10. Storageset Map To create a storageset map: 1. Copy the template from “Enclosure Template” in Appendix A. 2. Establish a local or remote connection to one of the controllers in your subsystem. Compaq HSZ80 Array Controller ACS Version 8.
3–36 Creating Storagesets 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. Use the following syntax: LOCATE device_name The LOCATE command causes the device’s LED to flash continuously. 5. Turn off the LED using the following syntax: LOCATE CANCEL The controller names each device based on its PTL location.
3–37 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. ■ L—Designates the LUN of the device. Place one space between the port number, target number, and the two-digit LUN number when entering the PTL address.
3–38 Creating Storagesets EMU 61500 61300 61200 61400 51500 51400 6 51300 41500 5 51200 31500 41300 41400 21500 41200 31400 31300 21400 4 21300 11200 3 31200 11300 12 2 21200 13 PVA 2 11500 14 11400 61100 51100 51000 50900 50800 61000 41100 41000 40900 40800 EMU 15 60900 31100 31000 30900 PVA 0 EMU Controller A Controller B Cache A Cache B 1 60800 21100 21000 20900 50100 0 50000 8 30800 40100 9 20800 40200 30100 11100 40300 30200 1 40000 11000 3030
3–39 When your controller receives an I/O request, it identifies the storageset unit number for the request, then correlates the unit number to the storageset name. From the storageset name, the controller locates the appropriate device for the I/O request. (For example, the RAIDset “RAID1” might contain DISK10000, DISK20000, and DISK30000.) The controller generates the read or write request to the appropriate device using the PTL addressing convention.
3–40 Creating Storagesets Planning Partitions Use partitions to divide a storageset or disk drive into smaller pieces, which can be presented to the host as its own storage unit. Figure 3–14 shows the conceptual effects of partitioning a single-disk unit. Partition 1 Partition 2 Partition 3 CXO-5316A-MC Figure 3–14. Partitioning a Single-Disk Unit You can create up to eight partitions per disk drive, RAIDset, mirrorset, stripeset, or striped mirrorset.
3–41 An unpartitioned storage unit has more capacity than a partition that uses the whole unit because each partition requires five blocks of administrative metadata. Thus, a single disk unit that contains one partition can store n-5 blocks of user or application data. See “Partitioning a Storageset or Disk Drive,” page 4–10, for information on manually partitioning a storageset or single-disk unit.
3–42 Creating Storagesets Choosing Switches for Storagesets and Devices Depending upon the kind of storageset or device you are configuring, you can enable the following 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 during the configuration process.
3–43 RAIDset Switches You can enable the following 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 spareset) that is on a different device port than the remaining operational disk drives.
3–44 Creating Storagesets ■ RECONSTRUCT=FAST gives more resources to reconstructing the replacement disk drive, which may reduce the subsystem’s overall performance during the reconstruction task. 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.
3–45 Mirrorset Switches You can enable the following switches to control how a mirrorset behaves to ensure data availability: ■ Replacement policy ■ Copy speed ■ Read source ■ Disaster Tolerance Support Replacement Policy Specify a replacement policy to determine how the controller replaces a failed disk drive: NOTE: If DT_SUPPORT is enabled, no policy can be selected.
3–46 Creating Storagesets Copy Speed Specify a copy speed to determine the speed with which the controller copies the data from an operational disk drive to a replacement disk drive: ■ COPY=NORMAL (default) balances the overall performance of the subsystem against the need for reconstructing the replacement disk drive. ■ COPY=FAST allocates more resources to reconstructing the replacement disk drive, which may reduce the subsystem’s overall performance during the reconstruction task.
3–47 Disaster Tolerance Support Specify if disaster tolerant functionality is supported by this mirrorset: ■ DT_SUPPORT is enabled if some members are or may be remote and disaster tolerant functionality is supported. The mirrorset has the following restrictions: NOPOLICY is enforced and NOWRITEBACK_CACHE is enforced ■ NODT_SUPPORT is enabled if all members are—and intend to remain—local, and if disaster tolerant functionality is not supported Compaq HSZ80 Array Controller ACS Version 8.
3–48 Creating Storagesets Device Switches When you add a disk drive or other storage device to your subsystem, you can enable the following switches: ■ Transportability (only disk drives) ■ Device transfer rate ■ Local/Remote (only disk drives) Transportability Indicate whether a disk drive is transportable when you add it to your subsystem: ■ NOTRANSPORTABLE disk drives (default) are marked with StorageWorksexclusive metadata.
3–49 Transportable devices have these characteristics: ❏ 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 storageset or spareset. ❏ Cannot be partitioned. ❏ Do not support forced errors.
3–50 Creating Storagesets Local/Remote Specify the disk characteristics in a mirrorset, either local (default) or remote. ■ Disks set to REMOTE can only be added to mirrorsets and JBOD (that is, not RAID5 raidsets). ■ Disks set to REMOTE can only be added to mirrorsets that are set to DT_SUPPORT. ■ Disks set to LOCAL can be added to mirrorsets that are set to either NODT_SUPPORT or DT_SUPPORT. ■ Disks set to REMOTE that are part of a mirrorset will not normally be the read source.
3–51 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 ■ Destroy/Nodestroy After you initialize the storageset or disk drive, you cannot change these switches without reinitializing the storageset or disk drive.
3–52 Creating Storagesets Increasing the Request Rate A large chunk size (relative to the average request size) increases the request rate by allowing multiple disk drives to respond to multiple requests. If one disk drive contains all of the data for one request, then the other disk drives in the storageset are available to handle other 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–15.
3–53 Large chunk sizes also tend to increase the performance of random reads and writes. It is recommended that you use a chunk size of 10 to 20 times the average request size, rounded up to the nearest multiple of 64. In general, a chunk size of 256 works well for UNIX® systems; 128 works well for OpenVMS™ systems. Increasing the Data Transfer Rate A small chunk size relative to the average request size increases the data transfer rate by allowing multiple disk drives to participate in one I/O request.
3–54 Creating Storagesets Increasing Sequential Write Performance For stripesets (or striped mirrorsets), use a large chunk size relative to the I/O size to increase the sequential write performance. A chunk size of 256 generally works well. Chunk size does not significantly affect sequential read performance. Maximum Chunk Size for RAIDsets Do not exceed the chunk sizes shown in Table 3–4 for a RAIDset.
3–55 Save Configuration Indicate whether to save the subsystem’s configuration on the storage unit when you initialize it: ■ NOSAVE_CONFIGURATION (default) means that the controller stores the subsystem’s configuration in its nonvolatile memory only. Although this is generally secure for single-controller configuration configurations, the configuration could be jeopardized if the controller fails.
3–56 Creating Storagesets ■ When you incorporate a spare into a storageset that you initialized with the INITIALIZE SAVE_CONFIGURATION command, the controller reserves space on the spare for configuration information. The controller updates this information when the configuration changes. ■ To enable SAVE_CONFIGURATION on a storageset containing user data, you must back up the data, re-initialize the storageset, and restore the user data.
3–57 ■ When replacing both controllers, you can replace the first and restart it alone by holding in port button 6 and pressing the reset button on the controller’s operator control panel. This controller picks up any previously saved configuration data on disk and uses it to set up the subsystem configuration. Replace the second controller using the SET FAILOVER COPY command to copy the configuration information from the operating controller.
3–58 Creating Storagesets Unit Switches You can enable (either add or set) the Unit switches listed in Table 3–5 for the listed storagesets and devices. See Chapter 5, “CLI Commands,” for an explanation of the following Unit switches.
4–1 Chapter 4 Configuring Storagesets This chapter provides information to help you configure storagesets for your subsystem. Compaq HSZ80 Array Controller ACS Version 8.
4–2 Configuring Storagesets Introduction One method of configuring storagesets is manual configuration. This method allows you the most flexibility in defining and naming storagesets. See Chapter 5, “CLI Commands,” for complete information about the CLI commands shown in this chapter. Adding Disk Drives The factory-installed devices in your StorageWorks subsystem have already been added to the controller’s list of eligible devices.
4–3 Configuring a Stripeset See “Using Striped Mirrorsets for Highest Performance and Availability,” page 3–18 for information about creating a profile and understanding the switches you can set for this kind of storage unit. To configure a stripeset: 1. Create the stripeset by adding its name to the controller’s list of storagesets and specifying the disk drives it contains. Use the following syntax: ADD STRIPESET stripeset-name DISKnnnn DISKnnnn 2. Initialize the stripeset.
4–4 Configuring Storagesets Example The following example shows the commands you would use to create Stripe1, a threemember stripeset: ADD STRIPESET STRIPE1 DISK10000 DISK20000 DISK30000 INITIALIZE STRIPE1 CHUNKSIZE=128 ADD UNIT D100 STRIPE1 MAXIMUM_CACHED_TRANSFER=16 SHOW STRIPE1 SHOW D100 Configuring a Mirrorset See “Creating a Storageset and Device Profile,” page 3–5, for information about creating a profile and understanding the switches you can set for this kind of storage unit.
4–5 3. Present the mirrorset to the host by giving it a unit number the host can recognize. Optionally, you can append Unit switch values. If you do not specify switch values, default values are applied. Use the following syntax: ADD UNIT unit-number mirrorset-name switch See “ADD UNIT,” page 5–27, for valid switches and values. 4. Verify the mirrorset configuration and switches. Use the following syntax: SHOW mirrorset-name 5. Verify the unit configuration and switches.
4–6 Configuring Storagesets Configuring a RAIDset See “Creating a Storageset and Device Profile,” page 3–5 for information about creating a profile and understanding the switches you can set for this kind of storage unit. To configure a RAIDset: 1. Create the RAIDset by adding its name to the controller’s list of storagesets and specifying the disk drives it contains. Optionally, you can append RAIDset switch values. If you do not specify switch values, default values are applied.
4–7 4. Verify the RAIDset configuration and switches. Use the following syntax: SHOW RAIDset-name 5. Verify the unit configuration and switches.
4–8 Configuring Storagesets 3. Initialize the stripeset. If you want to set any Initialize switches, you must do so in this step. Use the following syntax: INITIALIZE stripeset-name switch See “INITIALIZE,” page 5–62, for valid switches and values. 4. Present the stripeset to the host by giving it a unit number the host can recognize. Optionally, you can append Unit switch values. If you do not specify switch values, default values are applied.
4–9 Example The following example shows the commands you would use to create Stripe1, a threemember striped mirrorset that comprises Mirr1, Mirr2, and Mirr3, each of which is a two-member mirrorset: ADD MIRRORSET MIRR1 DISK10000 DISK20000 ADD MIRRORSET MIRR2 DISK30000 DISK40000 ADD MIRRORSET MIRR3 DISK50000 DISK60000 ADD STRIPESET STRIPE1 MIRR1 MIRR2 MIRR3 INITIALIZE STRIPE1 CHUNKSIZE=DEFAULT ADD UNIT D101 STRIPE1 SHOW STRIPE1 SHOW D101 Configuring a Single-Disk Unit Use the following steps to use a singl
4–10 Configuring Storagesets See “ADD UNIT,” page 5–27, for valid switches and values. 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 The following example shows the commands you would use to configure DISK10000 as a single-disk unit.
4–11 2. Initialize the storageset or disk drive. If you want to set any Initialize switches, you must do so in this step. Use the following syntax: INITIALIZE storageset-name switch 3. Create each partition in the storageset or disk drive by indicating the partition’s size. Use the following syntax: CREATE_PARTITION storageset-name SIZE=n where n is the percentage of the disk drive or storageset that will be assigned to the partition.
4–12 Configuring Storagesets Example The following example shows the commands you would use to create RAID1, a threemember RAIDset partitioned into four storage units: ADD RAIDSET RAID1 DISK10000 DISK20000 DISK30000 INITIALIZE RAID1 CREATE_PARTITION RAID1 SIZE=25 CREATE_PARTITION RAID1 SIZE=25 CREATE_PARTITION RAID1 SIZE=25 CREATE_PARTITION RAID1 SIZE=LARGEST SHOW RAID1 Partition number 1 2 3 4 . . . Size 1915 1915 1915 2371 (0.98 (0.98 (0.98 (1.
4–13 ADD UNIT D1 RAID1 PARTITION=1 ADD UNIT D2 RAID1 PARTITION=2 ADD UNIT D3 RAID1 PARTITION=3 ADD UNIT D4 RAID1 PARTITION=4 SHOW RAID1 . . . Partition number 1 Size 1915 (0.98 Starting Block 0 Used by D1 2 MB) 1915 (0.98 1920 D2 3 MB) 1915 (0.98 3840 D3 4 MB) 2371 (1.21 5760 D4 MB) . . . Adding a Disk Drive to the Spareset The spareset is a collection of hot spares that are available to the controller should it need to replace a failed member of a RAIDset or mirrorset.
4–14 Configuring Storagesets 2. Verify the contents of the spareset using the following syntax: SHOW SPARESET Example The following example shows the commands you would use to add DISK60000 and DISK60100 to the spareset. ADD SPARESET DISK60000 ADD SPARESET DISK60100 SHOW SPARESET Removing a Disk Drive from the Spareset You cannot delete the spareset—it always exists whether or not it contains disk drives.
4–15 Example The following example shows the commands you would use to remove DISK60000 from the spareset. SHOW SPARESET Name SPARESET Storageset spareset Uses disk60000 disk60100 Used by Uses disk60100 Used by DELETE SPARESET DISK60000 SHOW SPARESET Name SPARESET Storageset spareset 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.
4–16 Configuring Storagesets Deleting a Storageset If the storageset you are deleting is partitioned, you must delete each partitioned unit before you can delete the storageset. Use the following steps to delete a storageset: 1. Show the configuration using the following syntax: SHOW STORAGESETS 2. Delete the unit number shown in the “Used by” column. Use the following syntax: DELETE unit-number 3. Delete the name shown in the “Name” column. Use the following syntax: DELETE storageset-name 4.
4–17 Changing Switches for a Storageset or Device You can optimize a storageset or device at any time by changing the switches that are associated with it. See “Choosing Switches for Storagesets and Devices,” page 3–42, for an explanation of the switches. Remember to update the storageset’s profile (hardcopy) when you change its switches.
4–18 Configuring Storagesets Changing Initialize Switches The Initialize switches cannot be changed without destroying the data on the storageset or device. These switches are integral to the formatting and can only be changed by reinitializing the storageset. Initializing a storageset is similar to formatting a disk drive; all data is destroyed during this procedure. Changing Unit Switches Use the SET command to change Unit switches that are associated with a unit.
4–19 Configuring with the Command Console LUN The Command Console LUN (CCL) acts as a type of access device in the form of a LUN for communicating between the host and the controller. You can access the CCL using either StorageWorks Command Console (SWCC) or CLI commands. When the CCL is enabled, you can communicate between the controller and the host without a maintenance port cable.
4–20 Configuring Storagesets Finding the CCL Location To see where each CCL is located, use the following commands: SHOW THIS_CONTROLLER or SHOW OTHER_CONTROLLER Look under host port to find the Command Console LUN location. Because the CCL is not an actual device or unit, the SHOW UNITS command will display only unit information and no CCL locations.
4–21 CAUTION: Selecting SCSI-3 mode enables multiple CCLs—one for each target at LUN 0. If the hosts access the CCL simultaneously, unpredictable consequences can occur. In cases where the CCL can be accessed through multiple paths and LUNs, systems administrators of each host must not attempt to access the CCL simultaneously. Troubleshooting with the CCL Troubleshooting and maintaining the controller should not be done using the CCL.
4–22 Configuring Storagesets SCSI-2 Mode As you add storage units and set SCSI IDs over the CCL or above its location, the CCL immediately and automatically moves into the next available free space, which would be the lowest available Target ID/LUN setting. IMPORTANT: If you delete a unit at a setting below the CCL setting, the CCL does not automatically move to that setting. Instead, it only moves to the lowest deleted unit’s setting when you restart the controller.
4–23 Configuring Units with Multiple Hosts The HSZ80 Array Controller allows equal but separate access to the targets and units through multiple hosts running on different operating systems, which is called heterogeneous host support. The array controller allows hosts equal access to their targets and units by designating the host mode using the HOST_FUNCTION switch.
4–24 Configuring Storagesets The following modes can be assigned: ■ A—DIGITAL UNIX®, OpenVMS, and Hewlett-Packard® HP–UX (Default) ■ B—IBM AIX® ■ C—HSZ15 ■ D—Windows NTTM Server ■ E—Silicon Graphics Inc. IRIX ■ F—Sun Solaris For more information on the modes, see “SET controller,” page 5–91.
4–25 NOTE: Figure 4–1 shows an example of a heterogeneous host configuration. For supported host operating systems, refer to the HSZ80 Array Controller ACS Version 8.3 Release Notes. Host bus Windows NT Port 1 Digital OpenVMS Port 2 HSZ80 Controller device bus D0 D1 D2 D100 Controller device bus D101 D102 D200 D201 D202 D300 D301 D302 CXO6477A Figure 4–1.
4–26 Configuring Storagesets Transparent Failover Mode In transparent failover mode, units can be assigned to a host in a variety of setups, including these three common ways: ■ by designating the port of the controller, either Port 1 or Port 2 or both. ■ by designating the host SCSI ID number of the hosts configured on a shared bus. ■ by designating the port of the controller and by designating the host SCSI ID number of the hosts configured on a shared bus.
4–27 Windows NT Host bus Host bus Port 1 Digital UNIX Port 2 HSZ80 Controller device bus D100 Controller device bus D200 D300 D400 CXO6478A Figure 4–2.
4–28 Configuring Storagesets Designating the Host SCSI ID Number The HSZ80 Array Controller allows multiple hosts on the same SCSI host bus to access units individually and based on a host port’s SCSI ID number. The ENABLE_ACCESS_PATH syntax implements this access, but restricts each host on the same bus from accessing other hosts’ units.
4–29 Host bus SCSI ID 7 SCSI ID 6 Digital UNIX Sun Port 1 Port 2 HSZ80 Controller device bus D100 Controller device bus D102 D101 D103 CXO6479A Figure 4–3.
4–30 Configuring Storagesets Designating the Port and Designating the Host SCSI ID Number Using a two-step process, port access can be combined with shared host access on the same bus further restricting one host from accessing another host’s units. You start by assigning units on a port using the SET THIS PORT_n_ID command, followed by restricting access between hosts on the same host SCSI bus using the DISABLE_ACCESS_PATH and ENABLE_ACCESS_PATH switches.
4–31 r Host bus Host bus SCSI ID 7 Digital UNIX Windows NT SCSI ID 6 Port 1 Windows NT Port 2 HSZ80 Controller device bus D100 D101 D102 D103 D104 D200 D201 CXO6480A Figure 4–4.
4–32 Configuring Storagesets To assign the units to one of the Windows NT hosts using SCSI ID numbers, yet restrict the other Window NT host’s access, use the following syntax: SET D100 DISABLE_ACCESS_PATH = ALL SET D100 ENABLE_ACCESS_PATH = 7 SET D101 DISABLE_ACCESS_PATH = ALL SET D101 ENABLE_ACCESS_PATH = 7 SET D102 DISABLE_ACCESS_PATH = ALL SET D102 ENABLE_ACCESS_PATH = 6 SET D103 DISABLE_ACCESS_PATH = ALL SET D103 ENABLE_ACCESS_PATH = 6 SET D104 DISABLE_ACCESS_PATH = ALL SET D104 ENABLE_ACCESS_PATH =
4–33 NOTE: Figure 4–5 shows an example of a heterogeneous host configuration. For supported host operating systems, refer to the HSZ80 Array Controller ACS Version 8.3 Release Notes. Host bus SCSI ID 7 SCSI ID 6 Digital UNIX Windows NT SCSI ID 6 Port 1 Port 2 SCSI ID 7 HSZ80 controller A HSZ80 controller B Port 1 Port 2 Device bus D100 D101 D102 D200 D201 Host bus CXO6488A Figure 4–5.
4–34 Configuring Storagesets SET D101 THIS_PORT_1_DISABLE_ACCESS_PATH = ALL SET D101 OTHER_PORT_1_DISABLE_ACCESS_PATH = ALL SET D101 THIS_PORT_1_ENABLE_ACCESS_PATH = 7 SET D101 OTHER_PORT_1_ENABLE_ACCESS_PATH = 6 SET D102 THIS_PORT_1_DISABLE_ACCESS_PATH = ALL SET D102 OTHER_PORT_1_DISABLE_ACCESS_PATH = ALL SET D102 THIS_PORT_1_ENABLE_ACCESS_PATH = 7 SET D102 OTHER_PORT_1_ENABLE_ACCESS_PATH = 6 SET D200 THIS_PORT_1_DISABLE_ACCESS_PATH = ALL SET D200 OTHER_PORT_1_DISABLE_ACCESS_PATH = ALL SET D200 THIS_PORT
4–35 Moving Storagesets You can move a storageset from one subsystem to another without destroying its data as shown in Figure 4–6. You also can follow the steps in this section to move a storageset to a new location within the same subsystem. NOTE: You can use the procedure in this section to migrate wide devices from an HSZ70 controller in a BA370 rack-mountable enclosure to an HSZ80 environment.
4–36 Configuring Storagesets Use the following procedure to move a storageset while maintaining the data it contains: 1. Show the details for the storageset you want to move. Use the following syntax: SHOW storageset-name 2. Physically label each member with its name and PTL location. If you do not have a storageset map for your subsystem, you can enter the LOCATE command for each member to find its PTL location.
4–37 8. Recreate the storageset by adding its name to the controller’s list of valid storagesets and specifying the disk drives it contains. Although you have to recreate the storageset from its original disks, you do not have to add them in their original order. Use the following syntax: ADD storageset-name disk-name disk-name 9. Represent the storageset to the host by giving it a unit number the host can recognize.
4–38 Configuring Storagesets (...move 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 The following example shows the commands you would use to move the reduced RAIDset, R3, to another cabinet. R3 used to contain DISK20000, which failed before the RAIDset was moved. R3 contained DISK10000, DISK30000, and DISK40000 at the beginning of this example.
5–1 Chapter 5 CLI Commands This appendix contains the Command Line Interpreter (CLI) commands you can use to interact with your controller. Each command description contains the full syntax and examples of the use of the command. The Overview provides a general description of the CLI and how to use it. Compaq HSZ80 Array Controller ACS Version 8.
5–2 CLI Commands CLI Overview The Command Line Interpreter (CLI) is one of the user interfaces through which you control your StorageWorks array controller in the StorageWorks subsystem. The CLI commands allow you to manage the subsystem by viewing and modifying the configuration of the controller and the devices attached to them. You can also use the CLI to start controller diagnostic and utility programs.
5–3 ■ Device Commands—Create and configure containers made from physical devices attached to the controller. ■ Storageset Commands—Create and configure complex containers made from groups of device containers. There are four basic types of storagesets: stripesets, RAIDsets, striped-mirrorsets, and mirrorsets. Storageset commands group device containers together and allow them to be handled as single units. ■ Logical Unit Commands—Create and optimize access to logical units made from containers.
5–4 CLI Commands ■ The controller processes each command in sequence. You can continue entering subsequent commands while the controller is processing prior commands. A controller experiencing heavy data I/O may respond slowly to CLI commands. NOTE: Due to space limitations, some examples in this manual contain commands that exceed one line in length. In these instances, the paragraph preceding the example identifies which command is continued on the next line.
5–5 ■ The first character is a letter indicating the kind of device in the storage unit: use D for disk devices or P to indicate passthrough devices such as tape devices, loaders, and libraries. ■ If entered, the next one or two digits indicate which target ID number is to access the unit during normal operation. Use one of the controller’s SCSI target ID numbers assigned to the controller with the SET controller ID command. Omit leading zeroes for SCSI target ID numbers less than ten.
5–6 CLI Commands Changing the CLI Prompt You can change the CLI prompt that displays. Use the SET THIS_CONTROLLER PROMPT command. Enter a 1- to 16- character string as the new prompt. For example, you could use the prompt to indicate the array controller’s name, such as “HSZ>.” Command Syntax Commands to the controller must use the following command structure: COMMAND parameter SWITCHES ■ Command. A word or phrase expressed as a verb that is used to instruct the controller what to do.
5–7 ADD DISK Names a disk drive and adds it to the controller’s configuration. NOTE: The controller supports a maximum of 72 storage devices, even though more than 72 target IDs are available. Do not exceed the maximum number of devices in the subsystem. Syntax ADD DISK container-name scsi-port-target-lun Parameters container-name Assigns a name to the disk device. This is the name used with the ADD UNIT command to create a single-disk unit.
5–8 CLI Commands Switches NOTRANSPORTABLE (Default) TRANSPORTABLE Indicates whether a disk drive can be accessed exclusively by StorageWorks controllers. If the NOTRANSPORTABLE switch is specified, the controller makes a small portion of the disk inaccessible to the host. This restricted space is used to store information (metadata) used to improve data reliability, error detection, and the ability to recover data.
5–9 ■ Setting the switch to REMOTE forces a disk to be NOTRANSPORTABLE. TRANSFER_RATE_REQUESTED=ASYNCHRONOUS TRANSFER_RATE_REQUESTED=20MHZ (Default) TRANSFER_RATE_REQUESTED=10MHZ TRANSFER_RATE_REQUESTED=5MHZ Specifies the maximum data transfer rate at which the controller is to communicate with the disk drive. The user might need to limit the transfer rate to accommodate long cables between the controllers and the device.
5–10 CLI Commands This example creates a host-addressable unit after the disk is added: INITIALIZE DISK20000 2 0 0 ADD UNIT D199 DISK20000 This example shows how to add DISK200 as a remote disk drive to port 2, target 0, LUN 0: ADD DISK DISK200 2 0 0 REMOTE See also ADD MIRRORSET ADD UNIT DELETE container-name LOCATE SHOW DISKS SHOW DEVICES SET container-name
5–11 ADD MIRRORSET Names a mirrorset and adds it to the controller configuration. Syntax ADD MIRRORSET mirrorset-name disk-name1 [disk-nameN] Parameters mirrorset-name Assigns a name to the mirrorset. This is the name used with the ADD UNIT command to identify the mirrorset as a host-addressable unit. The mirrorset name must start with a letter (A through Z) and may consist of a maximum of nine characters including letters A through Z, numbers 0 through 9, periods (.), dashes (-), or underscores (_).
5–12 CLI Commands Specify COPY=FAST to allow the creation of mirrored data to take precedence over other controller operations. When you specify COPY=FAST, the controller uses more resources to create the mirrored data, and copying takes less time. However, overall controller performance is reduced. Specify COPY=NORMAL when operations performed by the controller should take priority over the copy operation. If you specify COPY=NORMAL creating the mirrored data has a minimal impact on performance.
5–13 Specify POLICY=BEST_FIT to choose a replacement disk drive from the spareset that equals or exceeds the base member size (smallest disk drive at the time the mirrorset was initialized). If there is more than one disk drive in the spareset that meets the criteria, the controller selects a disk drive with the best performance. This switch is not valid if DT_SUPPORT is enabled. Specify POLICY=BEST_PERFORMANCE to choose a replacement disk drive from the spareset with the best performance.
5–14 CLI Commands Specify READ_SOURCE=ROUND_ROBIN to sequentially direct read requests to each local mirrorset disk. The controller equally queries all normal local disks for each read request. If no normal local disk exists, then the controller will query the remote disks.
5–15 See also ADD DISK ADD UNIT DELETE container-name INITIALIZE MIRROR REDUCE SHOW mirrorset-name SHOW MIRRORSETS SHOW STORAGESETS UNMIRROR Compaq HSZ80 Array Controller ACS Version 8.
5–16 CLI Commands ADD PASSTHROUGH Creates a passthrough container. A passthrough container bypasses controller processing and allows the host to have direct access to the device. A passthrough device appears as if it were connected directly to the host bus rather than to the controller. Use passthrough containers to communicate with tape devices and tape loaders because they do not require the controller for optimum operation performance.
5–17 scsi-port-target-lun Indicates the SCSI device PTL address. Place one space between the port number, target number, and the two-digit LUN number when entering the PTL dress. See the “Device PTL Addressing Convention within the Controller,” page 3–36, for an explanation of the PTL addressing naming format. NOTE: See the HSZ80 Array Controller ACS Version 8.3 Release Notes to determine whether the disk drive you are planning to use is compatible with the controller.
5–18 CLI Commands See also ADD UNIT DELETE container-name SHOW DEVICES SHOW PASSTHROUGH SHOW passthrough-name
5–19 ADD RAIDSET Names a RAIDset and adds the RAIDset to the controller’s configuration. Compaq RAIDsets are often referred to as RAID level 3/5 storagesets because they use the best characteristics of RAID level 3 and RAID level 5. The number of members in the storageset is determined by the number of containers specified by the container-name parameter in the command. The data capacity of the RAIDset is determined by the storage size of the smallest member.
5–20 CLI Commands Switches POLICY=BEST_FIT POLICY=BEST_PERFORMANCE (Default) NOPOLICY Set the selection criteria the controller uses to choose a replacement member from the spareset when a RAIDset member fails. Specify POLICY=BEST_FIT to choose a replacement disk drive from the spareset that equals or exceeds the base member size (smallest disk drive at the time the RAIDset was initialized) of the remaining members of the RAIDset.
5–21 Specify NORMAL to balance other controller operations with the reconstruct operation. The controller uses relatively few resources to perform the reconstruct process: there is little impact on performance. REDUCED NOREDUCED (Default) Permits the addition of a RAIDset missing a member. Specify the REDUCED switch when you add a reduced RAIDset (a RAIDset that is missing a member). Specify the NOREDUCED switch when all the disks making up the RAIDset are present—for instance, when creating a new RAIDset.
5–22 CLI Commands ADD UNIT D70 RAID8 This example shows how you can create a three-member RAIDset from the members of a reduced four-member RAIDset. Do not initialize the RAIDset again. CAUTION: Data contained on the RAIDset will be erased if you reinitialize the RAIDset.
5–23 ADD SPARESET Adds a disk drive to the spareset. Syntax ADD SPARESET disk-name Parameter disk-name Indicates the name of the disk drive being added to the spareset. Only one disk drive can be added to the spareset with each ADD SPARESET command. Disks set to REMOTE cannot be added to the spareset.
5–24 CLI Commands ADD STRIPESET Names a stripeset and adds it to the controller configuration. Stripesets are sometimes referred to as RAID level 0 storagesets. The number of members in the stripeset is determined by the number of container-name parameters specified. Syntax ADD STRIPESET stripeset-name container-name1 container-name2 [container-nameN] Parameters stripeset-name Assigns a name to the stripeset.
5–25 Examples This example shows how to create a stripeset named STRIPE1 with three disks: DISK10000, DISK20100, and DISK30200: ADD DISK DISK10000 1 0 0 ADD DISK DISK20100 2 1 0 ADD DISK DISK30200 3 2 0 ADD STRIPESET STRIPE1 DISK10000 DISK20100 DISK30200 This example show how to create a stripeset named STRIPE1 and then create a logical unit from it: INITIALIZE STRIPE1 ADD UNIT D103 STRIPE1 This example shows how to create a two-member striped mirrorset (a stripeset whose members are mirrorsets), and how t
5–26 CLI Commands See also ADD UNIT ADD MIRRORSET DELETE container-name INITIALIZE SHOW STORAGESET SHOW STRIPESET SHOW stripeset-name
5–27 ADD UNIT Creates a logical unit from a device, container, or partition. The controller maps all requests from the host to the logical-unit number as requests to the container specified in the ADD UNIT command. If you add a newly created storageset or disk to your subsystem, you must initialize it before it can be added as a logical unit. If you are adding a storageset or disk that has data on it that you want to maintain, do not initialize it; it will be added as a logical unit.
CLI Commands Switches Table 5–3 lists all switches for the ADD UNIT command and identifies which switches may be used with each type of device or storageset. Descriptions of each switch follow the table.
5–29 ENABLE_ACCESS_PATH= DISABLE_ACCESS_PATH= THIS_PORT_1_ENABLE_ACCESS_PATH= THIS_PORT_1_DISABLE_ACCESS_PATH= THIS_PORT_2_ENABLE_ACCESS_PATH= THIS_PORT_2_DISABLE_ACCESS_PATH= OTHER_PORT_1_ENABLE_ACCESS_PATH= OTHER_PORT_1_DISABLE_ACCESS_PATH= OTHER_PORT_2_ENABLE_ACCESS_PATH= OTHER_PORT_2_DISABLE_ACCESS_PATH= Specifies the access path. It can be a single specific host ID, multiple host IDs, or all host IDs (ALL).
5–30 CLI Commands PARTITION=partition_number Identifies the unit number for a partition on a container. The partition-number identifies the partition associated with the unit number being added. Use the SHOW container-name command to find the partition numbers used by a storageset or a single-disk unit. NOTE: Do not split partitioned units across ports. Partitioned units must be on a single port.
5–31 Select PREFERRED_PATH=THIS_CONTROLLER to instruct “this controller” to bring the units online. Select PREFERRED_PATH=OTHER_CONTROLLER to instruct the “other controller” to bring the units online. See Chapter 2 for information regarding multiple bus failover. IMPORTANT: Subsystem performance is better if target ID numbers are balanced across the dual-redundant pair. READ_CACHE (Default) NOREAD_CACHE Sets the controller’s read-cache policy function.
5–32 CLI Commands RUN (Default) NORUN Controls the unit’s availability to the host. Specify RUN to make a unit available to the host. Specify NORUN to make a unit unavailable to the host and to cause any data in cache to be flushed to one or more drives. NORUN spins down all the disks used in the unit. The drives making up the unit spin down after the data has been completely flushed. NOTE: Do not specify the RUN and NORUN switches for partitions.
5–33 Specify WRITEBACK_CACHE for all new RAIDsets, mirrorsets, and units you want to take advantage of the controller’s write-back caching feature. WRITEBACK_CACHE cannot be enabled on units with an underlying DT_SUPPORT mirrorset container. Specify NOWRITEBACK_CACHE for units you want to receive data directly from the host without being cached.
5–34 CLI Commands See also CREATE_PARTITION DELETE unit-number SET unit-number SHOW UNITS
5–35 CLEAR_ERRORS CLI Stops the display of current or previous error messages at the CLI prompt. This command does not clear the error conditions, it only stops the display of errors at the CLI prompt. After the cause of the error condition has been corrected, issue the CLEAR_ERRORS CLI command to clear the error message. NOTE: There are three message types: info—general information; warning—user may want to examine, but command will be executed; and error—command will not execute.
5–36 CLI Commands CLEAR_ERRORS controller INVALID_CACHE Clears an invalid cache error and allows the controller and cache to resume operation. If the error is due to an incorrectly mirrored configuration, the controller indicates mirrored mode status after the error is cleared. Use this command for the following situations: ■ When the controller or cache modules have been replaced, resulting in mismatched data between the controllers.
5–37 Specify NODESTROY_UNFLUSHED_DATA in the following situations: ■ If the controller module has been replaced. ■ If the controller’s nonvolatile memory (NVMEM) has lost its contents. Specify DESTROY_UNFLUSHED_DATA in the following situations: ■ If the cache module has been replaced. ■ Any other reason not listed above. CAUTION: Specifying the DESTROY_UNFLUSHED_DATA switch destroys data remaining in cache, which can result in data loss.
5–38 CLI Commands CLEAR_ERRORS device-name UNKNOWN If a device failure causes the controller to label the device as unknown, the controller does not check the device again to see if it has been repaired or if the error condition has been corrected. You must enter this command so the controller can recognize the device after the cause of the error has been corrected.
5–39 See also CLEAR_ERRORS CLI CLEAR_ERRORS INVALID_CACHE CLEAR_ERRORS UNKNOWN CLEAR_ERRORS UNWRITEABLE_DATA Compaq HSZ80 Array Controller ACS Version 8.
5–40 CLI Commands CLEAR_ERRORS unit-number LOST_DATA Clears lost data errors on a unit and all partitions on the unit’s container are affected. The controller reports a lost data error on the unit when you remove a write-back cache module or when the cache module contains unflushed data, possibly due to an interruption in the primary power source with no backup power present. The CLEAR_ERRORS LOST_DATA command clears the lost data error but does not recover the lost data.
5–41 See also CLEAR_ERRORS CLI CLEAR_ERRORS INVALID_CACHE CLEAR_ERRORS UNKNOWN CLEAR_ERRORS UNWRITEABLE_DATA Compaq HSZ80 Array Controller ACS Version 8.
5–42 CLI Commands CLEAR_ERRORS unit-number UNWRITEABLE_DATA Clears an unwriteable data error on a unit. It affects all partitions on the same container. If a storageset or disk drive fails before its data has been written to it, the controller reports an unwriteable data error. The CLEAR_ERRORS UNWRITEABLE_DATA command removes the data from the cache and clears the unwriteable data error. CAUTION: This command causes data loss.
5–43 See also CLEAR_ERRORS CLI CLEAR_ERRORS INVALID_CACHE CLEAR_ERRORS LOST_DATA CLEAR_ERRORS UNKNOWN RETRY_ERRORS UNWRITEABLE_DATA Compaq HSZ80 Array Controller ACS Version 8.
5–44 CLI Commands CONFIGURATION RESET Erases the entire configuration on “this controller,” restores the controller’s default configuration, and shuts down the controller. NOTE: If you plan to use this feature, SAVE_CONFIGURATION must be set when you initialize the container. See “INITIALIZE,” page 5–62. Specify the CONFIGURATION RESET command on “this controller” in nofailover mode only.
5–45 CONFIGURATION RESTORE Copies a controller’s configuration from the disk configuration file into the controller’s non-volatile memory. This command locates the most recent configuration file created on disk and restores it. This command causes a reboot and takes effect immediately. Use this command for a single controller configuration only. Do not use it for controllers in a dual-redundant configuration.
5–46 CLI Commands See also CONFIGURATION RESET CONFIGURATION SAVE INITIALIZE
5–47 CONFIGURATION SAVE Forces a current copy of configuration information in a controller’s non-volatile memory into a configuration file on a disk. This allows the user to determine when a copy of the configuration is saved. Use this command to explicitly save a single controller’s configuration. The command takes effect immediately. In a dualredundant configuration, issue this command to both controllers.
5–48 CLI Commands CREATE_PARTITION Divides a non-transportable disk drive storageset into several, separately addressable storage units. The command marks a specified percentage of a disk drive or storageset to be used as a separately addressable unit. You can divide any nontransportable disk or storageset into a maximum of eight partitions. Each partition can be separately presented to the host. Partitions are not supported in multiple bus failover mode.
5–49 To create a partition, specify a percentage of the container’s total capacity. The entire container is then divided into segments equal to the percentage specified. For example, if SIZE=20, the container is divided into five (1.0/0.2=5) equal segments. The resulting partition is slightly smaller than the size specified because metadata also occupies some of partition’s allocated space.
5–50 CLI Commands Example This example shows how to create a RAIDset named RAID9 and divide it into four equal parts.
5–51 DELETE container-name Deletes a container belonging to the controller’s configuration. You cannot delete a container in use by a higher-level container. For example, you cannot delete a disk belonging to a member of a RAIDset, or a RAIDset unit; you must first delete the higher-level container or containers. NOTE: This command does not delete spareset or failedsets. You cannot delete spareset and failedset containers. See the DELETE FAILEDSET and DELETE SPARESET commands for details.
5–52 CLI Commands This example shows how to delete a RAIDset named RAID9: DELETE RAID9 See also DELETE FAILEDSET DELETE SPARESET UNMIRROR
5–53 DELETE FAILEDSET Removes a disk drive from the failedset. The failedset contains disk drives removed by the controller from RAIDsets and mirrorsets because they failed or were manually removed using the SET command. Enter the DELETE FAILEDSET command before physically removing failed members from the storage shelf for testing, repair, or replacement. You should consider defective all disk drives in the failedset. Repair or replace disks found in the failedset.
5–54 CLI Commands DELETE SPARESET Removes a disk drive from the spareset. Syntax DELETE SPARESET disk-name Parameter disk-name Identifies the disk drive being deleted from the spareset. Remove only one disk at a time from a spareset.
5–55 DELETE unit-number Deletes a logical unit from the controller configuration. The host cannot address deleted units. If the controller’s write-back caching feature is enabled, the controller flushes the cached data to the unit’s devices before deleting the unit. Before using the DELETE unit-number command, clear any errors with the CLEAR_ERRORS UNWRITEABLE_DATA or CLEAR_ERRORS LOST_DATA commands. Syntax DELETE unit-number Parameter unit-number Identifies the unit number to be deleted.
5–56 CLI Commands See also ADD UNIT CLEAR_ERRORS LOST_DATA CLEAR_ERRORS UNWRITEABLE_DATA DELETE container-name DELETE FAILEDSETS DELETE SPARESETS DESTROY_PARTITION
5–57 DESTROY_PARTITION Marks the area reserved for a partition as available. The freed area is then consolidated with any adjacent free areas. CAUTION: Data contained on a partition is lost when you enter the DESTROY_PARTITION command. You cannot destroy a partition that has been assigned a unit number. First enter the DELETE unit-number command to delete the unit using the partition. After you partition a container, you must initialize it in order to destroy the partitions.
5–58 CLI Commands Example This example shows how to delete the unit for partition 2 on RAIDset RAID9 and destroy the partition: DELETE D102 DESTROY_PARTITION RAID9 PARTITION=2 See also CREATE_PARTITION DELETE unit-number SHOW
5–59 DIRECTORY Lists the diagnostics and utilities available on “this controller.” Syntax DIRECTORY Example This example shows how to display a directory listing: DIRECTORY HSUTIL V83Z D FRUTIL V83Z D CHVSN V83Z D CLCP V83Z D CLONE V83Z D CONFIG V83Z D DILX V83Z D DIRECT V83Z D DSTAT V83Z D FMU V83Z D VTDPY V83Z D NOTE: CHVSN and DSTAT are not user utilities. They may be used by Compaq authorized service personnel only. See also RUN Compaq HSZ80 Array Controller ACS Version 8.
5–60 CLI Commands HELP Displays a brief explanation of how to use the question mark (?) to obtain help on any command or CLI function. You must precede the question mark with a space. Syntax HELP Example This example shows how to display information regarding the HELP command: HELP Help may be requested by typing a question mark (?) at the CLI prompt.
5–61 This example shows how to get help on the SET command using the question mark (?): SET ? Your options are: EMU FAILEDSET FAILOVER NOFAILOVER MULTIBUS_FAILOVER NOMULTIBUS_FAILOVER OTHER_CONTROLLER THIS_CONTROLLER . . . . . . . . . . . . . . . . . . . . . . Unit number or mirrorset or raidset or device name Compaq HSZ80 Array Controller ACS Version 8.
5–62 CLI Commands INITIALIZE Initializes or destroys metadata on a container. During initialization, a small amount of disk space is reserved for controller metadata and is made inaccessible to the host. Disks made transportable do not contain controller metadata. Syntax INITIALIZE container-name CAUTION: The INITIALIZE command destroys all user data on the container unless you enter the NODESTROY switch. The NODESTROY switch is only valid on mirrorsets and striped mirrorsets.
5–63 Parameters container-name Specifies the container to initialize. This is the same name given to the disk or storageset when it was created using the ADD command (for example, ADD DISK, ADD STRIPESET, and so forth). Switches CAPACITY= CYLINDERS= HEADS= SECTORS_PER_TRACK= CAPACITY may be specified 1 to the maximum container size (in blocks); CYLINDERS may be specified 1 to16,777,215; HEADS may be specified 1 to 255; and SECTORS_PER_TRACK may be specified 1 to 255.
5–64 CLI Commands The default chunk size for storagesets with less than nine members is 256 blocks, or 128 kilobytes (K). The default chunk size for storagesets with more than nine members is 128 blocks, or 64K. The default values provide optimal storageset performance for a wide variety of applications. A chunk size less than 128 blocks (64K) is not recommended. IMPORTANT: Accept the default chunk size setting for most applications.
5–65 The SAVE_CONFIGURATION switch requires only one disk to be initialized with this option. However, more disks may be used, if desired, for redundancy. Specify SAVE_CONFIGURATION to store a copy of the controller configuration on the container being initialized. A new controller can receive information from a container containing configuration information saved with the SAVE_CONFIGURATION switch.
5–66 CLI Commands TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 10.00 MHZ negotiated) LOCAL Size: 4108970 blocks Configuration being backed up on this container DISK30300 disk 3 3 0 S2 DEC RZ28M (C) DEC 1003 Switches: NOTRANSPORTABLE TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 10.00 MHZ negotiated) LOCAL Size: 4108970 blocks Configuration being backed up on this container This example shows how to initialize stripeset STRIPE1 with the default chunk size.
5–67 LOCATE Indicates the physical location of configured units, storagesets, and devices by flashing the amber device fault LED on the front of the storage building block (SBB). The device fault LED flashes once per second until turned off with the LOCATE CANCEL command. The LOCATE command can also be used to test the LED itself. The device fault LED on a failed device stays on continuously. When located, the device fault LED on a good device flashes.
5–68 CLI Commands DISKS Causes the green device fault LEDs of all configured disks to flash. Enter LOCATE CANCEL to turn off the LEDs. PTL (SCSI-location) Causes the green device fault LED on the device at the given SCSI location to flash. See “Device PTL Addressing Convention within the Controller,” page 3–36, for an explanation of the PTL addressing naming format. Not all devices have a device fault LED. Therefore, they do not appear to respond to the LOCATE command.
5–69 Examples This example shows how to cause the amber device fault LED on device DISK10000 to flash: LOCATE DISK10000 LOCATE CANCEL This example shows how to cause the device fault LEDs on all of the devices assigned to disk unit number D102 to flash: LOCATE D102 This example shows how to cause the device fault LEDs on all configured disk devices to flash: LOCATE DISKS This example shows how to turn off the flashing device fault LEDs on all devices: LOCATE CANCEL Compaq HSZ80 Array Controller ACS Versio
5–70 CLI Commands MIRROR Creates a one-member mirrorset from a single disk. This command is used only on disks configured as units or members of a stripeset. Enter the ADD MIRRORSET command to create a mirrorset from disk drives not already members of higher level containers.
5–71 Switches COPY=FAST COPY=NORMAL (Default) Sets the speed at which the controller copies data to a new member from normal mirrorset members when data is being mirrored to the storageset’s disk drives. Specify COPY=FAST to allow the creation of mirrored data to take precedence over other controller operations. When you specify COPY=FAST, the controller uses more resources to create the mirrored data, and copying takes less time. However, overall controller performance is reduced.
5–72 CLI Commands Specify POLICY=BEST_PERFORMANCE to choose a replacement disk drive from the spareset with the best performance. The controller attempts to select a disk on a different port than existing mirrorset members. If there is more than one disk drive in the spareset matching the best performance criteria, the controller selects a disk drive that equals or exceeds the base member size. This switch is not valid if DT_SUPPORT is enabled.
5–73 See also ADD MIRRORSET REDUCE SHOW MIRRORSETS UNMIRROR Compaq HSZ80 Array Controller ACS Version 8.
5–74 CLI Commands POWEROFF Powers off all disk units in a cabinet and turns off the cabinet power in all cabinets associated with the controller. Syntax POWEROFF Switches BATTERY _ON BATTERY_OFF (Default) Instructs the external cache battery (ECB) charger to turn off or remain on. Specify BATTERY_ON to keep the ECB powering the cache module after the cabinet is powered off. Specify BATTERY_OFF to disable the cache batteries after the cabinet is powered off.
5–75 SECONDS=nn As soon as the POWEROFF command is entered, all disk units in the cabinet are set to write-through. When the time interval, as represented by nn seconds, has elapsed, an orderly rundown of all units is started. When all units in the cabinet are successfully rundown, cabinet power is turned off.
5–76 CLI Commands Table 5–4 Poweroff Switch Settings (Continued) Battery Switch Override Switch Flush Results Action BATTERY_OFF OVERRIDE_BAD_FLUSH Success Controller and units in the cabinet are shutdown and the ECB is not powering the cache module. BATTERY_OFF OVERRIDE_BAD_FLUSH Failure Controller and units in the cabinet are shutdown and the ECB is not powering the cache module.
5–77 REDUCE Removes member disk drives from mirrorsets and decreases the nominal number of members in the mirrorsets. Unlike the SET mirrorset-name REMOVE=disk-name command, the controller does not put reduced members into the failedset. When using the REDUCE command to take a snapshot of a striped mirrorset, you must reduce all mirrorsets with one command. The CLONE utility does this automatically.
5–78 CLI Commands The actual number of members in the mirrorset can never be greater than the nominal number of members. The disks to be removed do not need to be members of the same mirrorset. However, the disks must all be part of the same unit (for example, the same striped mirrorset). When a disk is reduced from a mirrorset, the controller: ■ Pauses I/O to the unit. ■ Flushes all of the unit’s data from write-back data cache. ■ Removes the specified disks.
5–79 Example This example shows how to remove DISK20100, DISK20200, and DISK40200 from their respective mirrorsets: SHOW STRIPE1 Name Storageset Uses Used by ----------------------------------------------------------------------------STRIPE1 stripeset MIRR1 D104 MIRR2 MIRR3 SHOW MIRRORSETS Name Storageset Uses Used by ----------------------------------------------------------------------------MIRR1 mirrorset DISK10100 STRIPE1 DISK20100 MIRR2 mirrorset DISK10200 STRIPE1 DISK20200 MIRR3 mirrorset DISK30300
5–80 CLI Commands See also ADD MIRRORSET MIRROR RUN CLONE SHOW MIRRORSET SET mirrorset-name
5–81 RENAME Renames a container. Syntax RENAME old-container-name new-container-name Parameters old-container-name Specifies the existing name of the container. new-container-name Assigns the new name for the container. See “Changing the CLI Prompt,” page 5–6, for information regarding container naming rules. NOTE: Units may not be renamed.
5–82 CLI Commands RENAME DISK10000 MYDISK SHOW DISKS Name Type Port Targ Lun Used by ----------------------------------------------------------------MYDISK disk 1 0 0 D100 DISK10100disk 1 1 0 D101
5–83 RESTART controller Flushes all user data from the specified controller’s write-back cache and restarts the controller. Syntax RESTART controller Parameters controller The controller parameter indicates which controller is to be restarted. Specify OTHER_CONTROLLER or THIS_CONTROLLER. Switches IGNORE_ERRORS NOIGNORE_ERRORS (Default) Controls the reaction of the controller based on the status of write-back cache.
5–84 CLI Commands IMMEDIATE_SHUTDOWN NOIMMEDIATE_SHUTDOWN (Default) Instructs the controller when to shutdown. CAUTION: The IMMEDIATE_SHUTDOWN switch instructs the controller to immediately shutdown, without regard to any data contained within write-back cache. See “Fault-Tolerance for Write-Back Caching,” page 1–22 for considerations when implementing write-back cache. Do not perform any hardware changes until the controller flushes the cache.
5–85 RETRY_ERRORS unit-number UNWRITEABLE_DATA Causes the controller to attempt to write previously unwriteable data from the writeback cache to the devices. If a container fails, preventing the data in write-back cache to be written to the container, an unwriteable data error is reported. If possible, correct the condition that caused the unwriteable data and try the write operation again. No data is lost if the retry fails.
5–86 CLI Commands RUN Runs a diagnostic or utility program on “this controller.” Diagnostic and utility programs only run on “this controller.” Syntax RUN program-name Parameter program-name The program-name parameter specifies the name of the diagnostic or utility program to be run. The following programs can currently be run: ■ CHVSN—This is not a user utility. This utility may be used by Compaq authorized service personnel only. ■ CLCP—A utility used to load updated software code or patches.
5–87 CAUTION: Run the DILX utility in the autoconfigure mode only at initial installations. When write operations are enabled, the DILX utility may overwrite existing data. The autoconfigure mode is the most thorough mode and allows you to: ❏ Automatically test all of the disk units configured. ❏ Automatically perform thorough tests on all units with writes enabled. The standard mode is more flexible and allows you to: ❏ Test disks you select. ❏ Perform tests in read-only mode or write-only mode.
5–88 CLI Commands Example This example shows how to start the DILX diagnostic program: RUN DILX . . .
5–89 SELFTEST controller Flushes the data from the specified controller’s write-back cache (if present) and shuts down the controller. It then restarts the controller in self-test mode. Press the controller reset (//) button to take the controller out of self-test mode. Syntax SELFTEST controller Parameters controller The controller parameter indicates which controller is to perform the self-test program. Specify OTHER_CONTROLLER or THIS_CONTROLLER.
5–90 CLI Commands IMMEDIATE_SHUTDOWN NOIMMEDIATE_SHUTDOWN (Default) Instructs the controller whether to flush the write-back cache or not. CAUTION: The IMMEDIATE_SHUTDOWN switch instructs the controller to immediately shut down, without regard to any data contained within write-back cache. See “Fault-Tolerance for Write-Back Caching,” page 1–22, for considerations when implementing write-back cache. Do not perform any hardware changes until the controller flushes the cache.
5–91 SET controller Changes parameters on the specified controller. Syntax SET controller Parameter controller Indicates which controller is to be set. Specify OTHER_CONTROLLER or THIS_CONTROLLER. Switches Table 5–5 lists the switches available with this command. Descriptions of the switches follow the table.
5–92 CLI Commands Table 5–5 SET controller Switches (Continued) Switch Values PORT_1_ ID NOPORT_1_ID PORT_2_ID NOPORT_2_ID MIRRORED_CACHE NOMIRRORED_CACHE None PORT _1_PREFERRED_ID NOPORT_1_PREFERRED_ID PORT _2_PREFERRED_ID NOPORT_2_PREFERRED_ID PORT_1_TRANSFER_RATE_ REQUESTED NOPORT_1_TRANSFER_RATE_ REQUESTED PORT_2_TRANSFER_RATE_ REQUESTED NOPORT_2_TRANSFER_RATE_ REQUESTED 5MHz 10MHz 20MHz (default) PROMPT 1–16 characters SCSI_VERSION SCSI-2 (default) SCSI-3 TERMINAL_PARITY NOTERMINAL_PARITY
5–93 ALLOCATION_CLASS Allocation class is a unique identification number assigned to the controller pair under certain operating systems. The value for an allocation class is 1–4294967295. In DIGITAL Open VMS, this is a 2-byte number (do not specify a number over 65535); for DIGITAL UNIX, it is a 4-byte number. It is reported in response to the SCSI inquiry command and is the same for all units connected to one or both controllers.
5–94 CLI Commands CAUTION: Setting CACHE_UPS without having a UPS or similar backup system in place may result in data loss if power is interrupted. Specify NOCACHE_UPS to instruct the controller to perform regular cache battery checks and evaluate the condition of the cache batteries. Setting the CACHE_UPS switch for either controller sets the CACHE_UPS switch for both controllers.
5–95 The HOST_FUNCTION switch assigns only one host function to the specified target ID number with each SET command. You must enter separate SET commands to set multiple modes to different target ID number—for example, to support hosts with different operating systems on a single SCSI bus. Each controller or pair of controllers can service a maximum of two hosts simultaneously as long as they as they are assigned to different targets.
5–96 CLI Commands PORT_1_ID=(n1,n2,n3...) NOPORT_1_ID PORT_2_ID=(n1,n2,n3...) NOPORT_2_ID Assigns one to fifteen SCSI target ID numbers (0 through 15) to either port 1 or to port 2. A total of 15 target ID numbers can be assigned to both ports. For example, port 1 has eight target ID numbers and port 2 has seven target ID numbers for a total of 15. Another example, port 1 has 15 target ID numbers and port 2 has none.
5–97 The following tasks are performed when the NOMIRRORED_CACHE switch is specified: Both controllers must be operational before this command is accepted. ■ Data in write-back cache is flushed when cache is configured in non-mirrored mode. ■ Enables mirrored write-back cache on both controllers. ■ If an invalid cache configuration exists within the cache modules, an error is generated. Issue this switch through only one controller.
5–98 CLI Commands PORT_1_PREFERRED_ID=(n1,n2,n3...) NOPORT_1_PREFERRED_ID PORT_2_PREFERRED_ID=(n1,n2,n3...) NOPORT_2_PREFERRED_ID May be set only when dual-redundant configurations are operating in a transparent failover configuration. It specifies which targets and units are handled by the specified controller port. First, specify, the total set of ID numbers with the preferred ID number switch.
5–99 SCSI_VERSION=SCSI-2 (Default) SCSI_VERSION=SCSI-3 Specifies the host protocol to use; requires operating system support. SCSI-3 is limited SCSI-3. It also specifies how the command console LUN is handled. The command console LUN (CCL) presents to the GUI a virtual LUN through which it communicates with the controller. SCSI-2 specifies that the CCL is not fixed at a particular location, but floats depending on the configuration. SCSI-3 specifies that the LLC is fixed at LUN 0.
5–100 CLI Commands PORT_1_TRANSFER_RATE_REQUESTED=20MHZ PORT_1_TRANSFER_RATE_REQUESTED=10MHZ PORT_1_TRANSFER_RATE_REQUESTED=5MHZ PORT_1_TRANSFER_RATE_REQUESTED=DEFAULT NOPORT_1_TRANSFER_RATE_REQUESTED PORT_2_TRANSFER_RATE_REQUESTED=20MHZ PORT_2_TRANSFER_RATE_REQUESTED=10MHZ PORT_2_TRANSFER_RATE_REQUESTED=5MHZ PORT_2_TRANSFER_RATE_REQUESTED=DEFAULT NOPORT_2_TRANSFER_RATE_REQUESTED Specifies the maximum data transfer rate the controllers use when communicating with the host.
5–101 Examples This example shows how to change the other controller’s CLI prompt: SET OTHER_CONTROLLER PROMPT=“CONTROLLER B” This example shows how to set “this controller” on host port 1, so it responds to requests for target ID numbers 2 and 5: SET THIS_CONTROLLER PORT_1_ID=(2,5) See also SHOW THIS_CONTROLLER SHOW OTHER_CONTROLLER Compaq HSZ80 Array Controller ACS Version 8.
5–102 CLI Commands SET device-name Changes the transportable characteristics and the maximum data transfer rate between the controller and the specified device. Syntax SET device-name Parameter device-name Specifies the name of the device to change. This can be a previously named device, disk, passthrough device, or container. Switches LOCAL (Default) REMOTE Specifies the disk characteristics in a mirrorset, either local or remote.
5–103 TRANSFER_RATE_REQUESTED=ASYNCHRONOUS TRANSFER_RATE_REQUESTED=20MHZ (Default) TRANSFER_RATE_REQUESTED=10MHZ TRANSFER_RATE_REQUESTED=5MHZ Specifies the maximum data transfer rate for the controller to use in communicating with the device. You may need to limit the transfer rate to accommodate long cables between the controllers and the device. TRANSPORTABLE NOTRANSPORTABLE (Default) Indicates whether a disk can be accessed exclusively by StorageWorks controllers.
5–104 CLI Commands Examples This example shows how to set the data transfer rate of DISK20000 to 5MHz: SET DISK20000 TRANSFER_RATE_REQUESTED=5MHZ This example shows how to set DISK10300 to transportable: SET DISK10300 TRANSPORTABLE This example shows how to set DISK10300 to remote: SET DISK10300 REMOTE See also ADD DISK SHOW DISKS
5–105 SET EMU Sets operating parameters for the environmental monitoring unit (EMU). Syntax SET EMU Switches The SENSOR and FANSPEED switches control both the master and slave EMU settings. The EMU within the primary cabinet (master) instructs the EMUs within the other cabinets to operate at the same SENSOR and FANSPEED settings to which the master EMU is set.
5–106 CLI Commands .
5–107 The EMU instructs the fans to operate at high speed when any of the temperature setpoints are exceeded or when one or more fans are not functioning. Examples This example shows how to set EMU sensor number 2 to 34°C: SET EMU SENSOR_2_SETPOINT=34 This example shows how to set the EMU fan to operate at high speed: SET EMU FANSPEED=HIGH See also SHOW Compaq HSZ80 Array Controller ACS Version 8.
5–108 CLI Commands SET FAILEDSET Changes the automatic replacement policy for the failedset. Syntax SET FAILEDSET Switches AUTOSPARE NOAUTOSPARE Specifies the policy to be used by the controller when a disk drive is physically replaced in the failedset. Specify AUTOSPARE to instruct the controller to automatically move devices physically replaced in the failedset into the spareset. Disks set to REMOTE cannot be autospared.
5–109 Disks that you plan to use for AUTOSPARE must not have valid metadata on them. If you suspect a disk does have metadata on it (it was used in a stripeset or was initialized as NOTRANSPORTABLE) you must use the following steps to make the disk available as a spareset replacement disk: These steps use DISK10000 as an example. 1. Delete all containers to which the disk belongs. 2. Make the disk transportable. SET DISK10000 TRANSPORTABLE 3. Initialize the disk. INIT DISK10000 4. Delete the disk.
5–110 CLI Commands SET FAILOVER Configures both controllers to operate in a dual-redundant, transparent failover, configuration. This allows both controllers to access the storage devices, providing controller fault-tolerant data processing. If one of the two controllers fails, the devices and any cache attached to the failed controller become available to and accessible through the other controller.
5–111 Example This example shows how to set the controllers in a dual-redundant configuration and copy the configuration information from “this controller” to “other controller:” SET FAILOVER COPY=THIS_CONTROLLER See also SET MULTIBUS_FAILOVER SET NOFAILOVER SET NOMULTIBUS_FAILOVER Compaq HSZ80 Array Controller ACS Version 8.
5–112 CLI Commands SET mirrorset-name Changes the characteristics of a mirrorset, including the addition and removal of members. Syntax SET mirrorset-name Parameter mirrorset-name Specifies the name of the mirrorset to modify. This is the same name given to the mirrorset when it was created with the ADD MIRRORSET command.
5–113 DT_SUPPORT NODT_SUPPORT Specifies if disaster tolerant functionality is enabled on this mirrorset. If some members are or may be remote and disaster tolerant functionality is supported, set DT_SUPPORT. If all members are—and intend to remain—local and disaster tolerant functionality is not supported, set NODT_SUPPORT. If DT_SUPPORT is enabled, the mirrorset has the following restrictions: NOPOLICY is enforced and NOWRITEBACK_CACHE is enforced.
5–114 CLI Commands REMOVE=disk-name Instructs the controller to remove a member from an existing mirrorset. The disk drive specified by disk-name is removed from the mirrorset specified by mirrorset-name. The removed disk drive is added to the failedset. NOTE: No other switches can be set when the REMOVE switch is specified. If the mirrorset won’t have a normal or normalizing member remaining after you remove the disk drive, the controller reports an error and no action is taken.
5–115 ■ The replacement policy is set to NOPOLICY ■ The mirrorset is missing at least one member NOTE: An error is displayed if you attempt to replace a REMOTE disk into a NODT_SUPPORT mirrorset. If these conditions are met, the disk drive specified by disk-name is added to the mirrorset specified by mirrorset-name. The nominal number of members does not change. The disk name used is the name given to a disk when it was added to the configuration with the ADD DISK command.
5–116 CLI Commands Specify NOPOLICY to prevent the controller from automatically replacing a failed disk device. The mirrorset operates in a reduced state until a POLICY=BEST_FIT or POLICY=BEST_PERFORMANCE is selected, or a member is manually placed in the mirrorset. READ_SOURCE=disk-name READ_SOURCE=LEAST_BUSY (Default) READ_SOURCE=ROUND_ROBIN Selects the mirrorset member used by the controller to satisfy a read request. A member with REMOTE set may be selected.
5–117 This example shows how to remove member DISK30000 from mirrorset MIRR1 created above. If the mirrorset has a replacement policy and an acceptable disk drive is in the spareset, the controller automatically adds the spare disk drive to the mirrorset. SET MIRR1 REMOVE=DISK30000 This example shows how to add disk DISK30200 to the mirrorset MIRR1: SET MIRR1 REPLACE=DISK30200 A copy operation begins immediately on DISK30200.
5–118 CLI Commands SET MULTIBUS_FAILOVER Places “this controller” and the “other controller” into a dual-redundant (failover) configuration within a multiple-bus environment. This allows both controllers to access the storage devices and provide greater throughput. If one controller fails, the devices and cache attached to the failed controller become available to and accessible through the remaining controller.
5–119 Due to the amount of information being passed from one controller to the other, this command may take up to one minute to complete.
5–120 CLI Commands SET NOFAILOVER Reconfigures both controllers to operate in a nondual-redundant (nonfailover) configuration. Immediately after entering this command, remove one controller from the shelf because the sharing of devices is not supported by nonredundant controllers. NOTE: SET NOFAILOVER and SET NOMULTIBUS_FAILOVER have the same effect. Either command exits from transparent or multiple bus failover mode. It is recommended that both controllers be present when this command is carried out.
5–121 Specify NODESTROY_UNFLUSHABLE_DATA to leave the unwritten data intact in the failed controller’s write-back cache. When the failed controller is replaced and placed into service, the write-back cache data is flushed to the appropriate devices. Specify DESTROY_UNFLUSHABLE_DATA to reconfigure the operational controller before replacing the failed controller. The unwritten data of the failed controller may reference devices not present in the new configuration.
5–122 CLI Commands SET NOMULTIBUS_FAILOVER Reconfigures both controllers to operate in a non-dual-redundant (non-failover) configuration. Immediately after entering this command, remove one controller from the shelf because the sharing of devices is not supported by nonredundant controllers. NOTE: SET NOFAILOVER and SET NOMULTIBUS_FAILOVER have the same effect. Either command exits from transparent or multiple bus failover mode.
5–123 Under some circumstances, the data in a failed controller’s write-back cache may not fail over to the operating controller’s write-back cache. For example, cache data will not failover if the operating controller has a failed cache battery because of the risk of data loss if the power is interrupted. Specify NODESTROY_UNFLUSHABLE_DATA to leave the unwritten data intact in the failed controller’s write-back cache.
5–124 CLI Commands SET RAIDset-name Changes the characteristics of a RAIDset. Syntax SET RAIDset-name Parameters RAIDset-name Specifies the name of the RAIDset to modify. This is the name used with the ADD UNIT command to identify the RAIDset as a host-addressable unit. Switches POLICY=BEST_FIT POLICY=BEST_PERFORMANCE (Default) NOPOLICY Specifies the replacement policy to use when a member within the RAIDset fails.
5–125 RECONSTRUCT=FAST RECONSTRUCT=NORMAL (Default) Sets the speed at which the controller reconstructs the data on the new RAIDset member replacing a failed member. Specify NORMAL to balance other controller operations against the reconstruct operation. The controller uses relatively few resources to perform the reconstruct, and there is little impact on performance. Specify FAST when the reconstruct operation must take precedence over other controller operations.
5–126 CLI Commands REPLACE=disk-name Instructs the controller to add a disk member to an existing RAIDset if the following conditions are met: ■ The replacement policy is set to NOPOLICY. ■ The disk member is not in any configuration, including a spareset. An error is displayed and the command is rejected if the RAIDset is not in a reduced state, if a replacement policy is already specified, or if the disk specified is already being used by a configuration (including a spareset).
5–127 This example shows how to add disk DISK20100 to the reduced RAIDset, RAID9: SET RAID9 REPLACE=DISK20100 Reconstruction immediately begins on DISK20100. See also ADD RAIDSET SHOW RAIDSETS Compaq HSZ80 Array Controller ACS Version 8.
5–128 CLI Commands SET unit-number Changes the characteristics of a unit. Syntax SET unit-number Parameter unit-number Specifies the logical unit number to modify. The unit-number is the name given to the unit when it was created using the ADD UNIT command. Switches Table 5–8 lists all switches for the SET unit-number command and shows which switches can be used with each type of device and storageset. Descriptions of the switches follow the table.
5–129 Switch ACCESS PATH PARTITION=partition-number MAXIMUM_CACHED_ TRANSFER PREFERRED_PATH NOPREFERRED_PATH ERROR_MODE=NORMAL ERROR_MODE=FAILSAFE READ_CACHE NOREAD_CACHE READAHEAD_CACHE NOREADAHEAD_CACHE WRITE_PROTECT NOWRITE_PROTECT WRITEBACK_CACHE NOWRITEBACK_CACHE RUN NORUN Table 5–8 SET UNIT Switches for Existing Containers RAIDset ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Stripeset ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Mirrorset ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ NoTransportable Disk ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Transportable D
5–130 CLI Commands ENABLE_ACCESS_PATH= DISABLE_ACCESS_PATH= THIS_PORT_1_ENABLE_ACCESS_PATH= THIS_PORT_1_DISABLE_ACCESS_PATH= THIS_PORT_2_ENABLE_ACCESS_PATH= THIS_PORT_2_DISABLE_ACCESS_PATH= OTHER_PORT_1_ENABLE_ACCESS_PATH= OTHER_PORT_1_DISABLE_ACCESS_PATH= OTHER_PORT_2_ENABLE_ACCESS_PATH= OTHER_PORT_2_DISABLE_ACCESS_PATH= Specifies the access path. It can be a single specific host ID, multiple host IDs, or all host IDs (ALL).
5–131 PARTITION=partition_number Identifies the unit number for a partition on a container. The partition-number identifies the partition associated with the unit number being added. Use the SHOW container-name command to find the partition numbers used by a storageset or a single-disk unit. NOTE: Do not split partitioned units across ports. Partitioned units must be on a single port.
5–132 CLI Commands Select PREFERRED_PATH=THIS_CONTROLLER to instruct “this controller” to bring the unit online. Select PREFERRED_PATH=OTHER_CONTROLLER to instruct the “other controller” to bring the unit online. See Chapter 2 for information regarding multiple bus failover. ERROR_MODE=NORMAL ERROR_MODE=FAILSAFE Valid only on mirrorsets that have been enabled for DT_SUPPORT. Controls how the mirroring software treats member failure.
5–133 READAHEAD_CACHE (Default) NOREADAHEAD_CACHE Enables the controller to keep track of read I/Os. If the controller detects sequential read I/Os from the host, it will then try to keep ahead of the host by reading the next sequential blocks of data (those the host has not yet requested) and put the data in cache. This process is sometimes referred to as prefetch. The controller can detect multiple sequential I/O requests across multiple units.
5–134 CLI Commands Specify WRITE_PROTECT to prevent host write operations to the unit. However, the controller may still write to a write-protected RAIDset to satisfy a reconstruct pass or to reconstruct a newly replaced member. Additionally, metadata, reconstruct, and copy writes are still allowed to RAIDsets and mirrorsets. Specify NOWRITE_PROTECT to allow the host to write data to the unit. This allows the controller to overwrite existing data. NOWRITE_PROTECT is the default for transportable disks.
5–135 Example This example shows how to enable write protect and turn off the read cache on unit D102: SET D102 WRITE_PROTECT NOREAD_CACHE See also SHOW UNITS SHOW unit-number Compaq HSZ80 Array Controller ACS Version 8.
5–136 CLI Commands SHOW Displays information about controllers, storagesets, devices, partitions, and units. The SHOW command may not display some information for devices accessed through the companion controller in a dual-redundant configuration. When information regarding a device or parameter does not appear, enter the same SHOW command from a terminal on the other controller.
5–137 device-type Specifies the type of devices you want to be displayed. Valid choices are: ■ DEVICES—Shows all devices attached to the controller. ■ DISKS—Shows all disks attached to the controller. ■ PASSTHROUGH—Shows all passthrough containers attached to the controller. EMU Displays information regarding the status of the environmental monitoring unit (EMU). storageset-name Specifies the name of a particular storageset to be displayed.
5–138 CLI Commands UNITS Displays information for all units configured to the controller. If the underlying container is a mirrorset with DT_SUPPORT, it displays the ERROR_MODE setting. It reports if the mirrorset is failsafe locked or normal. A unit that is inoperative due to the failsafe locked condition will only be shown at the unit level (not mirrorset level). Since WRITEBACK_CACHE is not an allowable switch for DT_SUPPORT mirrorset, the switch is not displayed.
5–139 Examples This example shows how to display a listing of disks: SHOW DISKS Name Type Port Targ Lun Used by ----------------------------------------------------------------DISK20300 disk 1 0 0 D100 DISK10100 disk 1 1 0 D101 This example shows a full listing of devices attached to the controller: SHOW DEVICES FULL Name Type Port Targ Lun Used by -----------------------------------------------------------------------------DISK100 disk 1 0 0 R0 DEC HSZ80 (C) DEC V10Z Switches: NOTRANSPORTABLE TRANSFER_RA
5–140 CLI Commands Switches: NOTRANSPORTABLE TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 20.
5–141 DT_SUPPORT State: RECONSTRUCTING LOCAL DISK100 (member 0) is NORMAL REMOTE DISK200 (member 1) is NORMALIZING 2% complete LOCAL DISK300 (member 2) is NORMALIZING 0% complete REMOTE DISK400 (member 3) is NORMALIZING 0% complete Size: 8378028 blocks This example shows the full information for a controller: SHOW THIS_CONTROLLER FULL Controller: Not configured for dual-redundancy Device port SCSI address 7 Time: NOT SET Host port: SCSI target(s) (0, 2, 4, 5) Preferred target(s) (0, 2, 4) TRANSFER_RATE_RE
5–142 CLI Commands This example shows how to display the current settings for the EMU: SHOW EMU EMU CABINET SETTINGS SENSOR_1_SETPOINT 35 DEGREES C SENSOR_2_SETPOINT 35 DEGREES C SENSOR_3_SETPOINT 35 DEGREES C FANSPEED AUTOMATIC
5–143 SHUTDOWN controller Flushes all user data from the specified controller’s write-back cache (if present) and shuts down the controller. The controller does not automatically restart. All units accessed through the failed controller failover to the surviving controller. Syntax SHUTDOWN controller Parameter controller Indicates which controller is to shut down. Specify OTHER_CONTROLLER or THIS_CONTROLLER.
5–144 CLI Commands IMMEDIATE_SHUTDOWN NOIMMEDIATE_SHUTDOWN (Default) Instructs the controller when to shutdown. CAUTION: The IMMEDIATE_SHUTDOWN switch causes the controller to keep unflushed data in the write-back cache until it restarts and is able to write the data to devices. Do not perform any hardware changes until the controller flushes the cache.
5–145 UNMIRROR Converts a one-member mirrorset back to a non-mirrored disk drive and deletes its mirrorset from the list of known mirrorsets. This command can be used only on mirrorsets already members of higher-level containers (stripesets or units). The UNMIRROR command is not valid for disk drives having a capacity greater than the capacity of the existing mirrorset.
5–146 CLI Commands See also ADD MIRRORSET MIRROR REDUCE RUN CLONE SET mirrorset-name
A–1 Appendix A 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. Compaq HSZ80 Array Controller ACS Version 8.
A–2 System Profiles Device Profile Type of Storageset _____ Platter disk drive _____ Optical Disk Drive Device Name Unit Number Device Switches Transportability ___ No (default) ___ Yes Initialize Switches Chunk size ___ Automatic (default) ___ 64 blocks ___ 128 blocks ___ 256 blocks ___ Other: Unit Switches Read Cache ___ Yes (default) ___ No Availability ___ Run (default) ___ NoRun Save Configuration ___ No (default) ___ Yes Write Cache ___ Yes (default) ___ No Write Protection ___ No (default)
A–3 Storageset Profile Type of Storageset ___ Mirrorset ___ Storageset Name......... Disk Drives................... Unit Number.................
A–4 System Profiles Enclosure Template Power Power Supply Supply Power Power Supply Supply Power Power Supply Supply Power Power Supply Supply
B–1 Appendix B Controller Specifications This appendix contains physical, electrical, and environmental specifications for the HSZ80 Array Controller. Compaq HSZ80 Array Controller ACS Version 8.
B–2 Controller Specifications Physical and Electrical Specifications for the Controller Table B–1 lists the physical and electrical specifications for the controller and cache modules. Table B–1 Controller Specifications Hardware Length Width HSZ80 Array Controller module 12.5 inches 8.75 inches 23.27 W Write-back Cache, 512 MB 12.5 inches 7.75 inches 2.48 W (Battery charging) Power 8.72 W Current at +5 V Current at +12 V 6.
B–3 Environmental Specifications The HSZ80 array controller is intended for installation in a Class A computer room environment. The optimum environmental specifications are listed in Table B–2; the maximum operating environmental specifications are listed in Table B–3; and the maximum nonoperating environmental specifications are listed in Table B–4. These are the same as for other Compaq storage devices.
B–4 Controller Specifications Table B–3 Maximum Operating Environmental Specifications Condition Temperature Specification +10° to +40°C (+50° to +104°F) Derate 1.8°C for each 1000 m (1.
GL–1 Glossary This glossary defines terms pertaining to the HSZ80. 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. ACS Array Controller Software. See array controller software. array controller See controller. array controller software Software contained on a removable ROM program card that provides the operating system for the array controller.
GL–2 Glossary bit A single binary digit having a value of either 0 or 1. A bit is the smallest unit of data a computer can process. block Also called a sector. The smallest collection of consecutive bytes addressable on a disk drive. In integrated storage elements, a block contains 512 bytes of data, error codes, flags, and the block’s address header. bootstrapping A method used to bring a system or device into a defined state by means of its own action.
GL–3 cold swap A method of device replacement that requires the entire subsystem to be turned off before the SBB device can be replaced. See also hot swap and warm swap. command line interpreter The configuration interface to operate the controller software. configuration file A file that contains a representation of a storage subsystem’s configuration. container 1) Any entity that is capable of storing data, whether it is a physical device or a group of physical devices.
GL–4 Glossary 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. This technique is useful if the processor is capable of reading or writing data faster than a single disk can supply or accept the data. While data is being transferred from the first disk, the second disk can locate the next segment. device See node and peripheral device.
GL–5 dual-simplex A communications protocol that allows simultaneous transmission in both directions in a link, usually with no flow control. DUART Dual Universal Asynchronous Receiver and Transmitter. An integrated circuit containing two serial, asynchronous transceiver circuits. ECB External Cache Battery. The unit that supplies backup power to the cache module in the event the primary power source fails or is interrupted. ECC Error Checking and Correction. EDC Error Detection Code.
GL–6 Glossary FD SCSI The fast, narrow, differential SCSI bus with an 8-bit data transfer rate of 10 MB/s. See also FWD SCSI and SCSI. flush The act of writing dirty data from cache to a storage media. FMU Fault Management Utility. forced errors A data bit indicating a corresponding logical data block contains unrecoverable data. FRU Field Replaceable Unit. A hardware component that can be replaced at the customer’s location by Compaq service personnel or qualified customer service personnel.
GL–7 host compatibility mode A setting used by the controller to provide optimal controller performance with specific operating systems. This improves the controller’s performance and compatibility with the specified operating system. hot disks A disk containing multiple hot spots. Hot disks occur when the workload is poorly distributed across storage devices which prevents optimum subsystem performance. See also hot spots. hot spots A portion of a disk drive frequently accessed by the host.
GL–8 Glossary I/O module A 16-bit SBB shelf device that integrates the SBB shelf with either an 8-bit single ended, 16-bit single-ended, or 16-bit differential SCSI bus. I/O operation The process of requesting a transfer of data from a peripheral device to memory (or vice versa), the actual transfer of the data, and the processing and overlaying activity to make both of those happen. JBOD Just a Bunch of Disks. Describes a group of single-device logical units. LBN Logical Block Number.
GL–9 MB/s Megabytes per second. Approximately one million (106) bytes per second. 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. The maintenance terminal is not required for normal operations. See also local terminal. member A container that is a storage element in a RAID array.
GL–10 Glossary normal member A mirrorset member that, block-for-block, contains the same data as other normal members within the mirrorset. Read requests from the host are always satisfied by normal members. 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.
GL–11 parity check A method of detecting errors when data is sent over a communications line. With even parity, the number of ones in a set of binary data should be even. With odd parity, the number of ones should be odd. PCM Polycenter Console Manager. PCMCIA Personal Computer Memory Card Industry Association. An international association formed to promote a common standard for PC card-based peripherals to be plugged into notebook computers.
GL–12 Glossary protocol The conventions or rules for the format and timing of messages sent and received. PTL Port-Target-LUN. The controller’s method of locating a device on the controller’s device bus. PVA module Power Verification and Addressing module. RAID Redundant Array of Independent Disks. Represents multiple levels of storage access developed to improve performance or availability or both. RAID level 0 A RAID storageset that stripes data across an array of disk drives.
GL–13 RAID level 3/5 A Compaq-developed RAID storageset that stripes data and parity across three or more members in a disk array. A RAIDset combines the best characteristics of RAID level 3 and RAID level 5. A RAIDset is the best choice for most applications with small to medium I/O requests, unless the application is write intensive. A RAIDset is sometimes called parity RAID. Raid level 3/5 storagesets are sometimes referred to as RAIDsets. RAIDset See RAID level 3/5.
GL–14 Glossary RFI Radio Frequency Interference. The disturbance of a signal by an unwanted radio signal or frequency. replacement policy The policy specified by a switch with the SET FAILEDSET command indicating whether a failed disk from a mirrorset or RAIDset is to be automatically replaced with a disk from the spareset. The two switch choices are AUTOSPARE and NOAUTOSPARE. SBB Storage Building Block.
GL–15 SCSI ID number The representation of the SCSI address that refers to one of the signal lines numbered 0 through 15. SCSI-P cable A 68-conductor (34 twisted-pair) cable generally used for differential bus connections. SCSI port (1) Software: The channel controlling communications to and from a specific SCSI bus in the system. (2) Hardware: The name of the logical socket at the back of the system unit to which a SCSI device is connected.
GL–16 Glossary storage subsystem The controllers, storage devices, shelves, cables, and power supplies used to form a mass storage subsystem. 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.
GL–17 surviving controller The controller in a dual-redundant configuration pair that serves its companion’s devices when the companion controller fails. synchronous Pertaining to a method of data transmission which allows each event to operate in relation to a timing signal. See also asynchronous. tape A storage device supporting sequential access to variable sized data records. target (1) A SCSI device that performs an operation requested by an initiator.
GL–18 Glossary VHDCI Very High Density Cable Interface. A 68-pin interface. Required for Ultra SCSI connections. virtual terminal A software path from an operator terminal on the host to the controller’s CLI interface, sometimes called a host console. The path can be established via the host port on the controller (using HSZterm) or via the maintenance port on the controller. VTDPY Virtual Terminal Display utility.
GL–19 write-through cache A cache management technique for retaining host write requests in read cache. When the host requests a write operation, the controller writes data directly to the storage device. This technique allows the controller to complete some read requests from the cache, greatly improving the response time to retrieve data. The operation is complete only after the data to be written is received by the target storage device.
I–1 Index A AC input module parts, 1–4 ADD DISK, 5–7 LOCAL, 5–8 NOTRANSPORTABLE, 5–8 REMOTE, 5–8 TRANSFER_RATE_REQUESTED, 5–9 TRANSPORTABLE, 5–8 ADD DISK container-name scsi-port-targetlun, 5–7 ADD MIRRORSET, 5–11 COPY, 5–11 DT_SUPPORT, 5–12 NODT_SUPPORT, 5–12 POLICY, 5–12 READ_SOURCE, 5–13 ADD PASSTHROUGH, 5–16 TRANSFER_RATE_REQUESTED, 5–17 ADD PASSTHROUGH passthrough-name scsi-port-target-lun, 5–16 ADD RAIDSET, 5–19 NOPOLICY, 5–20 NOREDUCED, 5–21 POLICY, 5–20 RECONSTRUCT, 5–20 REDUCED, 5–21 ADD RAIDSET
I–2 Index Addresses providing with the PVA module, 2–25 Addressing PTL convention, 3–36 ALLOCATION_CLASS SET controller, 5–93 Array of disk drives, 3–8 AUTOSPARE, 4–15 SET FAILEDSET, 5–108 Autospare failedset, 4–15 Availability, 3–15 B BA370 rack-mountable enclosure parts, 1–4 Backing up data, 3–20 Backing up data with the Clone utility, 1–16 Backplane location, 1–8 Backup power source enabling write-back caching, 1–22 Battery hysteresis, 1–31 BATTERY_OFF POWEROFF, 5–74 BATTERY_ON POWEROFF, 5–74 Building
I–3 write-through caching, 1–21 Cache policies fault-tolerance for write-back caching, 1–22 Cache, setting flush timer, 5–93 CACHE_FLUSH_TIMER SET controller, 5–93 CACHE_UPS SET controller, 5–93 Caching techniques general description, 1–20 read caching, 1–20 read-ahead caching, 1–20 write-back caching, 1–21 write-through caching, 1–21 CAPACITY CREATE_PARTITION, 5–49 INITIALIZE, 5–63 Change volume serial number utility.
I–4 Index CLEAR_ERRORS unit-number UNWRITEABLE_DATA, 5–42 CONFIGURATION RESET, 5–44 CONFIGURATION RESTORE, 5–45 CONFIGURATION SAVE, 5–47 CREATE_PARTITION, 5–48 customizing the prompt, 5–98 DELETE container-name, 5–51 DELETE FAILEDSET, 5–53 DELETE SPARESET, 5–54 DELETE unit-number, 5–55 DESTROY_PARTITION, 5–57 DIRECTORY, 5–59 getting help, 5–3 HELP, 5–60 INITIALIZE, 5–62 LOCATE, 5–67 MIRROR, 5–70 overview, 5–2 POWEROFF, 5–74 REDUCE, 5–77 RENAME, 5–81 RESTART controller, 5–83 RETRY_ERRORS unit-number UNWRIT
I–5 CONFIGURATION RESET, 5–44 CONFIGURATION RESTORE, 5–45 Configuration rules devices, 2–2 LUN capacity, 2–2 mirrorsets, 2–2 partitions per storageset, 2–2 RAID-5 and RAID-1 storagesets, 2–2 RAID-5 storagesets, 2–2 RAID-5, RAID-1, and RAID-0 storagesets, 2–2 requirements, 2–2 striped mirrorsets, 2–2 stripesets, 2–2 See also Summary of controller features CONFIGURATION SAVE, 5–47 Configuration utility.
I–6 Index OCP, 1–8, 1–13 other controller defined, 2–28 part numbers of parts used in configuring, 1–10 parts, 1–4 parts used in configuring, 1–10 patching controller software with the CLCP utility, 1–16 program card, 1–8 relationship to cache module, 1–13 release lever, 1–8 replacing a failed controller with FRUTIL, 1–17 reset button on the OCP, 1–14 showing, 5–136 shutting down, 5–143 single-controller configuration, 2–15 summary of features, 1–5 testing with DILX, 1–16 this controller defined, 2–28 tra
I–7 DELETE container-name, 5–51 DELETE FAILEDSET, 5–53 DELETE FAILEDSET disk-name, 5–53 DELETE SPARESET, 5–54 DELETE SPARESET disk-name, 5–54 DELETE unit-number, 5–55 Deleting devices, 5–51 mirrorsets, 5–51 RAIDsets, 5–51 storagesets, 5–51 stripesets, 5–51 units, 5–55 Deleting storagesets, 4–16 DESTROY, 3–57 INITIALIZE, 5–64 DESTROY_PARTITION, 5–57 DESTROY_PARTITION container-name PARTITION=partition-number, 5–57 DESTROY_UNFLUSHABLE_DATA SET NOFAILOVER, 5–120 SET NOMULTIBUS_FAILOVER, 5–122 DESTROY_UNFLUSHE
I–8 Index DILX general description, 1–16 DILX, running, 5–86 DIMMs cache module memory configurations, 1–18 supported, 1–5 DIRECT, running, 5–87 DIRECTORY, 5–59 DISABLE_ACCESS SET unit-number, 5–130 DISABLE_ACCESS_PATH ADD UNIT, 5–29 Disabling autospare, 4–15 Disaster tolerance write-back caching not enabled in disastertolerant mirrorsets, 1–21 Disaster tolerance support, 3–47 Disk drives adding, 4–2 adding to configuration, 5–7 adding to spareset using CLI, 4–13 adding with the CONFIG utility, 1–16 array
I–9 Dual-redundant configuration ECB, 1–29 Dual-redundant controller configuration disabling, 5–120, 5–122 enabling, 5–110 Dual-redundant controller configurations connecting to the host, 2–15 multiple-bus failover mode, 2–30 transparent failover mode, 2–29 when to use, 2–29 E ECB as a default backup source, 1–22 battery hysteresis, 1–31 diagnostics, 1–31 dual-battery ECB, 1–4 general description, 1–29 maintenance period, 1–29 replacing ECBs with FRUTIL, 1–17 single-battery ECB, 1–4 Electrostatic discharg
I–10 Index Failover disabling, 5–120, 5–122 general description, 2–29 multiple-bus, 2–30 transparent, 2–29 FAILSAFE, error mode, 5–132 Failures displaying with FMU, 1–15 setting display characteristics with FMU, 1–15 FANSPEED SET EMU, 5–106 Fault LEDs, 1–13 Fault management utility. See FMU Fault-management software. See FMU Fault-tolerance for write-back caching general description, 1–22 nonvolatile memory, 1–22 Field Replacement utility.
I–11 HSUTIL, running, 5–87 HSZ80 Array Controller Subsystem. See Storage subsystem HSZ80 Array Controller. See Controller HSZterm. See remote connection Hysteresis.
I–12 Index CANCEL, 5–67 container-name, 5–68 DISKS, 5–68 parameter, 5–67 PTL (SCSI-location), 5–68 unit-number, 5–68 UNITS, 5–68 Lost data error, clearing, 5–40 LUN, 2–2 largest device, storageset, or unit, 1–6 M Maintenance port establishing a local connection to the controller, 2–26 general description, 1–14 location, 1–8 precautions, xvii terminal or PC connection, 2–26 See also Maintenance port cable, Terminal connection Maintenance port cable establishing a local connection to the array controller,
I–13 description, 3–2, 3–12 displaying information, 5–136 duplicating data with the Clone utility, 1–16 initializing, 5–62 maximum number of members, 2–2 planning, 3–13 removing a member, 5–77 renaming, 5–81 setting a replacement policy, 5–20 showing, 5–136 temporary from CLONE, 3–20 unmirroring, 5–145 write-back caching not enabled in disastertolerant mirrorsets, 1–21 Moving storagesets, 4–35 MTBF, See Mean time between failures Multiple-bus failover configuration when to use, 2–30 Multiple-bus failover m
I–14 Index NOPORT_2_ID SET controller, 5–96 NOPORT_2_PREFERRED_ID SET controller, 5–98 NOPORT_2_TRANSFER_RATE_REQUEST ED SET controller, 5–100 NOPREFERRED_PATH ADD UNIT, 5–30 SET unit-number, 5–131 NOREAD_CACHE ADD UNIT, 5–31 SET unit-number, 5–132 NOREADAHEAD_CACHE ADD UNIT, 5–31 SET unit-number, 5–133 NOREDUCED ADD RAIDSET, 5–21 NORUN ADD UNIT, 5–32 SET unit-number, 5–133 NOSAVE_CONFIGURATION, 3–55 INITIALIZE, 5–64 Note, defined, xix NOTERMINAL_PARITY SET controller, 5–99 NOTRANSPORTABLE, 3–48 ADD DISK,
I–15 guidelines, 3–41 maximum supported, 1–5, 2–2 planning, 3–40 setting size, 5–48 showing, 5–136 Parts AC input module, 1–4 BA370 rack-mountable enclosure, 1–4 cache module, 1–4 controller, 1–4 cooling fan, 1–4 disk drives, 1–4 dual-battery ECB, 1–4 ECB, 1–4 EMU, 1–4 I/O module, 1–4 power cable, 1–4 power cable kit, 1–4 power supply, 1–4 PVA module, 1–4 SCSI hub, 3-port, 1–4 SCSI hub, 5-port, 1–4 SCSI hub, 9-port, 1–4 single-battery ECB, 1–4 Passthrough adding to configuration, 5–16 Passthrough container
I–16 Index See also Device ports, Host ports Power cable parts, 1–4 Power cable kit parts, 1–4 Power source enabling write-back caching, 1–22 Power supply parts, 1–4 Power, verification, and addressing module.
I–17 changing characteristics, 5–124 changing switches, 4–17 choosing chunk size, 3–51 configuring using CLI, 4–6 deleting, 5–51 description, 3–2, 3–15 displaying information, 5–136 initializing, 5–62 maximum chunk size, 3–54 maximum membership, 3–17 planning, 3–16 removing a member, 5–125 renaming, 5–81 replacing a member, 5–126 specifying replacement policy, 5–124 switches, 3–43 Read caching enabled for all storage units, 1–20 general description, 1–20 READ_CACHE ADD UNIT, 5–31 SET unit-number, 5–132 REA
I–18 Index Restoring configuration, 5–45 RETRY_ERRORS unit-number UNWRITEABLE_DATA, 5–85 Revision history, xxii RUN, 5–86 ADD UNIT, 5–32 CHVSN, 5–86 CLCP, 5–86 CLONE, 5–86 CONFIG, 5–86 DILX, 5–86 DIRECT, 5–87 DSTAT, 5–87 FMU, 5–87 FRUTIL, 5–87 HSUTIL, 5–87 SET unit-number, 5–133 VTDPY, 5–87 RUN program name, 5–86 S Save configuration, 3–55 SAVE_CONFIGURATION, 3–55 INITIALIZE, 5–64 Saving configurations, 5–47 dual-redundant configurations, 3–56 SCSI device ports. See Device ports SCSI device targets.
I–19 PORT_1_PREFERRED_ID, 5–98 PORT_1_TRANSFER_RATE_REQUESTE D, 5–100 PORT_2_ID, 5–96 PORT_2_PREFERRED_ID, 5–98 PORT_2_TRANSFER_RATE_REQUESTE D, 5–100 PROMPT, 5–98 SCSI_VERSION, 5–99 TERMINAL_PARITY, 5–99 TERMINAL_SPEED, 5–99 TIME, 5–99 TRANSFER_RATE_REQUESTED, 5–100 SET device-name, 5–102 LOCAL, 5–102 NOTRANSPORTABLE, 5–103 REMOTE, 5–102 TRANSFER_RATE_REQUESTED, 5–103 TRANSPORTABLE, 5–103 SET EMU, 5–105 FANSPEED, 5–106 SENSOR_N_SETPOINT, 5–105 SET FAILEDSET, 5–108 AUTOSPARE, 5–108 NOAUTOSPARE, 5–108 SET F
I–20 Index controller behavior at restart, 5–84 controller behavior at shutdown, 5–144 controller behavior selftest, 5–90 controller cache flush timer, 5–93 controller cache UPS policy, 5–93 controller configuration handling, 5–64 controller error handling at selftest, 5–84, 5–89 controller error handling at shutdown, 5–143 data retention policy, 5–36 device data transfer rate, 5–9, 5–103 failedset autospare feature, 5–108 fan speed, 5–106 full display, 5–138 mirrorset copy data, 5–71 mirrorset copy speed
I–21 Single-disk units backing up, 3–20 configuring using CLI, 4–9 displaying switches, 4–17 SIZE CREATE_PARTITION, 5–48 Spareset removing a disk drive, 5–54 Sparesets adding disk drives using CLI, 4–13 adding to configuration, 5–23 AUTOSPARE, 4–15 removing disk drives using CLI, 4–14 Specify device addresses, ?? to 3–37 Speed.
I–22 Index description, 3–2, 3–9 displaying information, 5–136 initializing, 5–62 maximum number of members, 1–6, 2–2 mirroring, 5–70 planning, 3–10 renaming, 5–81 showing, 5–136 specifying chunksize, 5–63 Subsystem addressing with the PVA module, 2–25 connecting a single controller to the host, 2–9 connecting dual-redundant controllers to the host, 2–15 connecting multiple-bus failover, dualredundant controllers to the host, 2–21 illustration of SCSI target ID numbers and PVA settings, 2–25 saving config
I–23 This controller defined, 2–28 This controller, defined, xviii Tightening VHDCI cables, xvii TIME SET controller, 5–99 Tip, defined, xix Tools, xx Topology supported, 1–5 Transfer rate how chunk size affects, 3–51 setting device, 5–9, 5–103 switch, 3–49 TRANSFER_RATE_REQUESTED, 3–49 ADD DISK, 5–9 ADD PASSTHROUGH, 5–17 SET controller, 5–100 SET device-name, 5–103 Translating messages FMU, 1–15 Transparent failover mode configuring units with multiple hosts, 4–26 designating the host SCSI ID number, 4–28
I–24 Index See also Config utility See also HSUTIL Troubleshooting and maintaining the controller utilities and exercisers, 1–15 Typographical conventions, xviii U Unit switches changing, 4–18 overview, 3–58 Units adding to configuration, 5–27 changing characteristics, 5–128 clearing lost data error, 5–40 configuring with multiple hosts, 4–23 deleting from the configuration, 5–55 displaying configured units, 5–138 displaying information, 5–136 heterogeneous host support, 4–23 largest unit supported, 1–6,
I–25 VTDPY, running, 5–87 W Write performance, 3–54 WRITE_PROTECT ADD UNIT, 5–32 SET unit-number, 5–133 Write-back caching enabled for all disk units, 1–21 fault-tolerance, 1–22 general description, 1–21 not enabled in disaster-tolerant mirrorsets, 1–21 setting the flush timer, 5–93 WRITEBACK_CACHE ADD UNIT, 5–32 SET unit-number, 5–134 Write-through caching enabling and disabling, 1–21 general description, 1–21 Compaq HSZ80 Array Controller ACS Version 8.
