DIGITAL HSG80 Array Controller ACS Version 8.2 EK-HSG80-UG.
July 1998 While Digital Equipment Corporation believes the information included in this manual is correct as of the date of publication, it is subject to change without notice. DIGITAL makes no representations that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
iii Preface Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Electrostatic Discharge Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii Component Precaution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Maintenance Port Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix Conventions . . . . . . . . . . . . . . . . . . . . . .
iv Selecting a Cache Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12 Fault-Tolerance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–12 Backing up Power with a UPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13 Connecting the Subsystem to the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14 Connecting a Dual-Redundant Configuration to the Host . . . . . . . . . . . .
v Replacement Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–40 Reconstruction Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–40 Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–41 Mirrorset Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3–42 Replacement Policy . . . . . . . . . . . . . . . . . . . .
vi Chapter 4 Troubleshooting Maintenance Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1 Troubleshooting Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2 Troubleshooting Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–4 Significant Event Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii Replacing the External Cache Battery Storage Building Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–27 Replacing the External Cache Battery Storage Building Block With Cabinet Powered On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5–28 Replacing the External Cache Battery Storage Building Block With Cabinet Powered Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii Appendix A System Profiles Device Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–2 Storageset Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–3 Enclosure Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A–4 Appendix B CLI Commands CLI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ix HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–69 INITIALIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–71 LOCATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–77 MIRROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–79 POWEROFF . . . . . . . . . . .
x Failover Event Sense Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–6 Nonvolatile Parameter Memory Component Event Sense Data Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D–8 Backup Battery Failure Event Sense Data Response . . . . . . . . . . . . . . . . . . .D–9 Subsystem Built-In Self Test Failure Event Sense Data Response . . . . . . .D–10 Memory System Failure Event Sense Data Response . . . . . . . . . . . . .
xi Figures The HSG80 Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–3 A Host and Its Storage Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–7 HSG80 Array Controller–Fibre Channel Copper Cabling. . . . . . . . . . . . . . . . . . .1–8 Optional Maintenance Port Cable for a Terminal Connection. . . . . . . . . . . . . . .1–10 HSG80 Array Controller–Fibre Channel Optical Cabling. . . . . . . . . . . . . . . . . .
xii Parity Ensures Availability; Striping Provides Good Performance. . . . . . . . . . . 3–15 Striping and Mirroring in the Same Storageset. . . . . . . . . . . . . . . . . . . . . . . . . . 3–17 CLONE Steps for Duplicating Unit Members . . . . . . . . . . . . . . . . . . . . . . . . . . 3–20 Controller Port ID and Unit Numbers in Transparent Failover Mode . . . . . . . . 3–28 Controller Port ID Numbers and Unit Numbers in Mulitple Bus Failover Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xiii Template 05 - Failover Event Sense Data Response Format . . . . . . . . . . . . . . . . D–7 Template 11 - Nonvolatile Parameter Memory Component Event Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–8 Template 12 - Backup Battery Failure Event Sense Data Response Format . . . . D–9 Template 13 - Subsystem Built-In Self Test Failure Event Sense Data Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xv Tables Key to Figure 1–1 The HSG80 Subsystem . . . . . . . . . . . . . . . . . . .1–3 Controller Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–4 Key to Figure 1–3 HSG80 Array Controller–Fibre Channel Copper Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1–9 Key to Figure 1–4: Optional Maintenance Port Cable for a Terminal Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi VTDPY Key Sequences and Commands . . . . . . . . . . . . . . . . . . . . . 4–23 Device Map Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–25 Device Status Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–26 Device-Port Status Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–28 Unit Status Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvii Preface This book describes the features of the HSG80 array controller and configuration procedures for the controller and storagesets running Array Controller Software (ACS) Version 8.2G. This book does not contain information about the operating environments to which the controller may be connected, nor does it contain detailed information about subsystem enclosures or their components. See the documentation that accompanied these peripherals for information about them.
xviii Precautions Follow these precautions when 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.
xix Component Precaution System components referenced in this manual comply to regulatory standards documented herein. Use of other components in their place may violate country standards, negate regulatory compliance, or invalidate the warranty on your product. Maintenance Port Precautions The maintenance port generates, uses, and radiates radio-frequency energy through cables that are connected to it. This energy may interfere with radio and television reception.
xx Conventions This book uses the following typographical conventions and special notices to help you find what you’re looking for. Typographical Conventions Convention ALLCAPS BOLD Meaning Command syntax that must be entered exactly as shown, for example: SET FAILOVER COPY=OTHER_CONTROLLER ALLCAPS Monospaced Sans serif italic italic Command discussed within text, for example: “Use the SHOW SPARESET command to show the contents of the spareset.” Screen display.
xxi 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.
xxii Required Tools You will need the following tools to service the controller, cache module, external cache battery (ECB), the Power Verification and Addressing (PVA) module, the Gigabit Link Module (GLM), and the I/O module: n n n n n 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.
xxiii Related Publications The following table lists some of the documents that are related to the use of the controller, cache module, and external cache battery.
xxiv Revision History This is a revised document. Previous documents include: EK-HSG80-UG .A01 ACS Version 8.
1–1 CHAPTER 1 General Description This chapter illustrates and describes in general terms your subsystem and its major components: the HSG80 array controller, its cache module, and its external cache battery. See the Fibre Channel Arbitrated Loop Hub User’s Guide and the KGPSA PCI-to-Fibre Channel Host Adapter User Guide for information about the fibre channel arbitrated loop hub and adapter that connect the subsystem to your host.
1–2 HSG80 User’s Guide The HSG80 Array Controller Subsystem Take a few moments to familiarize yourself with the major components of the HSG80 Array Controller subsystem. Figure 1–1 shows the components of a typical installation which includes: n n n n n n n One BA370 rack-mountable pedestal enclosure. Two controllers, each supported by their own cache module.
General Description 1–3 Figure 1–1 The HSG80 Subsystem 12 1 11 4x 2 10 9 3 6x 8 7 6 5 4 CXO6453A Table 1–1 Key to Figure 1–1 The HSG80 Subsystem Item Description Part No.
1–4 HSG80 User’s Guide Table 1–1 Key to Figure 1–1 The HSG80 Subsystem (Continued) Item Description Part No. 11 180-watt power supply DS–BA35X–HH 12 ECB, single ECB, dual DS–HS35X–BC DS–HS35X–BD Summary of HSG80 Features Table 1–2 summarizes the features of the controller.
General Description 1–5 Table 1–2 Controller Features (Continued) Feature Device protocol Device bus interconnect Number of SCSI device ports Number of SCSI device targets per port Maximum number of SCSI devices Disk Drives RAID levels supported Cache Capacity n n n n n n n n n n n n n n n Caching Features Maximum number of RAID-5 and RAID-1 storagesets Maximum number of RAID-5 storagesets n n n n Supported SCSI–2 Limited SCSI–3 Ultra/Fast Wide Singleended 6 12 72 4 and 9 GB Ultra & Fast Wide 18 GB
1–6 HSG80 User’s Guide Table 1–2 Controller Features (Continued) Feature Maximum number of RAID-5, RAID-1, and RAID-0 storagesets Maximum number of partitions per storageset or individual disk Maximum number of units presented to each host Maximum number of devices per unit Serial interconnect speed Maximum device, storageset, or unit size Configuration Save n 45 n 8 n n n n n n General Features Supported n n n n n 16 (8 on each of 2 ports) This is a driver limitation.
General Description 1–7 The HSG80 Array Controller Your controller is the intelligent bridge between your host and the devices in your subsystem. As Figure 1–2 illustrates, it bridges the gap between the host and its storage subsystem. Figure 1–2 A Host and Its Storage Subsystem Storage subsystem Host Hub Controller CXO6233B The controller is an integral part of any storage subsystem because it provides a host with high-performance and high-availability access to storage devices.
1–8 HSG80 User’s Guide controller processes the I/O requests, the host isn’t burdened by the processing that’s typically associated with reading and writing data to multiple storage devices. For the most recent list of supported devices and operating systems, see the product-specific release notes that accompanied your controller’s software. To determine which specific parts you need for your configuration, see “Connecting the Subsystem to the Host,” page 2–14.
General Description Table 1–3 Key to Figure 1–3 HSG80 Array Controller–Fibre Channel Copper Cabling Item Description Part No.
1–10 HSG80 User’s Guide Figure 1–4 Optional Maintenance Port Cable for a Terminal Connection 1 2 3 4 5 CXO6485A Table 1–4 Key to Figure 1–4: Optional Maintenance Port Cable for a Terminal Connection Item Description Part Number 1 BC16E-xx Cable Assembly 17–04074–01 2 Ferrite Bead 16–25105–14 3 RJ-11 Adapter 12–43346–01 4 RJ-11 Extension Cable 17–03511–01 5 PC Serial Port Adapter, 9 pin D-sub to 25 pin SKT D-sub for a PC 12–45238–01 PC Serial Port Adapter, 9 pin D-sub to 25 pin D-sub
General Description 1–11 Figure 1–5 HSG80 Array Controller–Fibre Channel Optical Cabling 1 2x 1 2 3 4 5 6 2 2x CXO6494A Table 1–5 Key to Figure 1–4 HSG80 Array Controller–Fibre Channel Optical cabling Item Description Part No.
1–12 HSG80 User’s Guide distinctive “snap” sound. This will indicate that the cable is properly inserted into the controller. Fibre Channel Optical Cable Cleaning Instructions It is essential to maintain clean cables to ensure optimum performance and lifespan of the cable. Figure 1–6 illustrates the proper cleaning procedures, as outlined in the following steps: 1. Open the prep cleaner using the lever on the side of the cable cartridge. 2. Rotate the end face of the ferrule 180 degrees. 3.
General Description 1–13 The HSG80 Array Controller components that you will use most often, such as the maintenance port and the OCP, are conveniently located on the controller’s front panel. The host port and program-card slot are also located on the front panel, making it easy to update the controller’s software or to connect the controller to a different host. Each controller is supported by its own cache module.
1–14 HSG80 User’s Guide Figure 1–8 HSG80 Controller Operator Control Panel (OCP) Reset button/ LED 1 Port button/ LED 2 3 4 5 6 CXO6216A To identify the exact location of the OCP, refer to Figure 1–3. 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.
General Description 1–15 Fault Management Utility The Fault Management Utility (FMU) provides a limited interface to the controller’s fault-management system. As a troubleshooting tool, you can use FMU to display last-failure and memory-system-failure entries, translate many of the code values contained in event messages, and set the display characteristics of significant events and failures. See “Fault Management Utility,” page 4–17, for more information about using this utility.
1–16 HSG80 User’s Guide HSUTIL Use HSUTIL to upgrade the firmware on disk drives in the subsystem and to format disk drives. See “Upgrading Firmware on a Device,” page 6–11, for more information about this utility. Code Load and Code Patch Utility Use Code Load/Code Patch (CLCP) utility to upgrade the controller software and the EMU software. You can also use it to patch the controller software. When you install a new controller, you must have the correct software version and patch number.
General Description 1–17 Change Volume Serial Number Utility Only DIGITIAL authorized service personnel may use this utility. The Change Volume Serial Number (CHVSN) utility generates a new volume serial number (called VSN) for the specified device and writes it on the media. It is a way to eliminate duplicate volume serial numbers and to rename duplicates with different volume serial numbers.
1–18 HSG80 User’s Guide Cache Module Each controller requires a companion cache module as shown in Figure 1–9. Figure 1–7 on page 1–13 shows the location of a controller’s companion cache module. The cache module, which can contain up to 512 MB of memory, increases the subsystem’s I/O performance by providing read, read-ahead, write-through, and write-back caching.
General Description Figure 1–9 Cache Module 5 4 1 ~ 2 3 2x CXO6161A Item Description Part No.
1–20 HSG80 User’s Guide Caching Techniques The cache module supports the following caching techniques to increase the subsystem’s read and write performance: n n n n 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 stores the data in its cache module. This process is called read caching.
General Description 1–21 Write-Through Caching When the controller receives a write request from the host, it stores the data in its cache module, writes the data to the disk drives, then notifies the host when the write operation is complete. This process is called write-through caching because the data actually passes through—and is stored in—the cache memory on its way to the disk drives. If you enable read caching for a storage unit, write-through caching is automatically enabled.
1–22 HSG80 User’s Guide THIS CONTROLLER CACHE_UPS command. See Appendix B, “CLI Commands,” for instructions on using this command. Cache Policies Resulting from Cache Module Failures If the controller detects a full or partial failure of its cache module or ECB, it automatically reacts to preserve the unwritten data in its cache module.
General Description 1–23 Table 1-7 Cache Policies and Cache Module Status (Continued) Cache Module Status Cache Policy Cache A Cache B Unmirrored Cache Mirrored Cache DIMM or cache memory controller chip failure Good 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–24 HSG80 User’s Guide Table 1-7 Cache Policies and Cache Module Status (Continued) Cache Module Status Cache Policy Cache A Cache B Unmirrored Cache Mirrored Cache Cache Board Failure Good Same as for DIMM failure. 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.
General Description Table 1-8 Cache Policies Resulting and ECB Status (Continued) Cache Module Status Cache Policy Cache A Cache B Unmirrored Cache Mirrored Cache Less than 50% charged At least 50% charged Data loss: No Data loss: No Cache policy: Controller A supports write-through caching only; controller B supports writeback caching. Cache policy: Both controllers continue to support write-back caching. Failover: No Failover: In transparent failover, all units failover to controller B.
1–26 HSG80 User’s Guide Table 1-8 Cache Policies Resulting and ECB Status (Continued) Cache Module Status Cache Policy Cache A Cache B Unmirrored Cache Mirrored Cache Failed At least 50% charged Data loss: No Data loss: No Cache policy: Controller A supports write-through caching only; controller B supports writeback caching. Cache policy: Both controllers continue to support write-back caching.
General Description 1–27 Table 1-8 Cache Policies Resulting and ECB Status (Continued) Cache Module Status Cache Policy Cache A Cache B Unmirrored Cache Mirrored Cache Failed Less than 50% charged 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: No Failover: In transparent failover, all units failover to controller B and operate normally.
1–28 HSG80 User’s Guide 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 external cache battery (ECB) or a UPS. DIGITAL supplies two versions of ECBs: a single-battery ECB for single controller configurations, and a dual-battery ECB for dualredundant controller configurations, which is shown in Figure 1–10.
General Description 1–29 When the batteries are fully charged, an ECB can preserve 512 MB of cache memory for 24 hours. However, the battery capacity depends upon the size of memory contained in the cache module, as defined in the Table 1–9.
1–30 HSG80 User’s Guide Note If a UPS is used for backup power, the controller does not check the battery. See Appendix B, “CLI Commands,” for information about the CACHE_UPS and NOCACHE_UPS switches.
2–1 CHAPTER 2 Configuring an HSG80 Array Controller This chapter explains how to configure an HSG80 Array Controller and the modules that support its operation in a StorageWorks subsystem.
2–2 HSG80 User’s Guide Introduction Use the Getting Started 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. For the complete syntax and descriptions of the CLI commands used in the configuration procedure, see Appendix B, “CLI Commands.
Configuring an HSG80 Array Controller 2–3 Configuring an HSG80 Array Controller You can use this procedure to configure your controller in one of the following ways: n n n Single controller Dual controllers (in transparent failover mode) Multiple-bus failover (host-assisted), dual-redundant controllers References sited in the steps below will help you locate details about the commands and concepts. Use the following steps to configure an HSG80 array controller: 1.
2–4 HSG80 User’s Guide If this is a single configuration with a single hub, set PORT 2 off-line. If this is a dual-redundant configuration, the “other controller” inherits “this controller’s” port topology. See Appendix B, “CLI Commands,” for more information about using the SET THIS_CONTROLLER PORT_n_TOPOLOGY= command. 8. If you selected LOOP_HARD for the port topology, specify the arbitrated loop physical address (ALPA) for the host ports.
Configuring an HSG80 Array Controller 2–5 If you’re configuring dual-redundant controllers, also change the CLI prompt on the “other controller.” Use the following syntax: SET OTHER_CONTROLLER PROMPT = “new prompt” See Appendix B, “CLI Commands,” for more information about using the SET OTHER_CONTROLLER PROMPT= command. 12. Optional: Indicate that your subsystem power is supported by a UPS.
2–6 HSG80 User’s Guide 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 array controllers. Use PVA IDs 2 and 3 for the additional enclosures. Figure 2–1 illustrates the PVA settings in an extended subsystem.
Configuring an HSG80 Array Controller 2–7 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 Getting Started Guide that came with your platform kit for details.
2–8 HSG80 User’s Guide Caution The local-connection 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. Do not leave any cables connected to it when you are not communicating with the controller. Follow these steps to establish a local connection for setting the controller’s initial configuration: 1.
Configuring an HSG80 Array Controller Figure 2–3 “This Controller” and “Other Controller” Other controller This controller CXO6468B 2–9
2–10 HSG80 User’s Guide Selecting a Failover Mode When selecting a failover mode, use transparent failover if you want the failover to occur without any intervention from the host, or employ multiple-bus failover if you want the host to send commands to the companion array controller. Using Transparent Failover Transparent failover is a dual-redundant controller configuration in which two controllers are connected to the same host and device buses.
Configuring an HSG80 Array Controller 2–11 Using Multiple-Bus Failover Multiple-bus (or host-assisted) failover is a dual-redundant controller configuration in which each array controller has its own connection to the host. Thus, if one of the host connections to an array controller fails, the host can cause units that became inaccessible to failover to the remaining viable connection.
2–12 HSG80 User’s Guide Enabling Mirrored Write-Back Cache Before configuring dual-redundant controllers and enabling mirroring, ensure the following conditions are met: n n n n n Both array controllers support the same size cache, 64 MB, 128 MB, 256MB, or 512 MB. Diagnostics indicates that both caches are good. Both caches have a battery present, if you have not enabled the CACHE_UPS switch. A battery does not have to be present for either cache if you enable the CACHE_UPS switch.
Configuring an HSG80 Array Controller 2–13 Backing up Power with a UPS By default, the controller expects to use an external cache battery (ECB) as backup power to the cache module. You can also opt to use an uninterruptable power supply (UPS) to provide backup power in the event of a primary power failure. See Appendix B, “CLI Commands,” for details about the SET THIS_CONTROLLER CACHE_UPS command. See Table 1-7 on page 1–22 and Table 1-8 on page 1–24 for information about cache policies.
2–14 HSG80 User’s Guide Connecting the Subsystem to the Host This section describes how to connect your subsystem to a host. It also includes instructions for connecting a single (nonredundant) controller and dual-redundant controllers to the host. Caution Do not attempt to configure dual-redundant controllers using one hub with a loopback cable. This configuration will cause data corruption and is not supported.
Configuring an HSG80 Array Controller 2–15 Use the following steps to connect a single, nonredundant controller to the host using one hub: 1. Stop all I/O from the host to its devices on the bus to which you are connecting the controller. 2. Connect the Fibre Channel cable from Port 1 on the controller to Port 1 of the hub. For this configuration, set Port 2 off-line using the SET THIS_CONTROLLER PORT_2_TOPOLOGY=OFFLINE command. See Appendix B, “CLI Commands,” for details about the SET command. 3.
2–16 HSG80 User’s Guide Table 2–2 Key to Figure 2–5 Cabling for Single Configuration (optical) Item Description Part No. 1 Single Controller 70–33259–xx 2 .
Configuring an HSG80 Array Controller 2–17 Connecting a Dual-Redundant Controller Configuration to the Host There are two possible ways to connect dual-redundant controllers to your host. The first method requires two hubs; the second method requires one hub. Using Two Hubs Use the following steps and Figure 2–6 to connect your dual-redundant controllers to the host using two hubs with copper support.
2–18 HSG80 User’s Guide 1. Stop all I/O from the host to its devices on the bus to which you are connecting the controllers. 2. Connect the Fibre Channel cable from Port 1 on controller A to Port 9 on hub 1. Repeat this step to connect the second cable from Port 1 on controller B to Port 8 on hub 1. 3. Connect another Fibre Channel cable from Port 2 on controller A to Port 1 on hub 2. Repeat this step to connect the final cable from Port 2 on controller B to Port 2 on hub 2. 4.
Configuring an HSG80 Array Controller 2–19 Use the following steps and Figure 2–7 to connect your dual-redundant controllers to the host using two hubs with optical support: Figure 2–7 Cabling for Dual-Redundant Configuration with Two Hubs using Fibre Channel Optical Support 2 To host 1 1 1 2 2 3 3 4 4 5 5 6 6 2 3 To host CXO6496A
2–20 HSG80 User’s Guide Table 2–4 Key to Figure 2–7 Cabling for Dual-Redundant Configuration with Two Hubs (optical) Item Description Part No. 1 Dual Controller — 2 12-Port Fibre Channel HUB DHGGA-CA 3 .
Configuring an HSG80 Array Controller 2–21 Using One Hub Use the following steps and Figure 2–8 to connect your dual-redundant controllers to the host using one hub with copper support: Figure 2–8 Cabling for Dual-Redundant Configuration with One Hub using Fibre Channel Copper Support 1 1 1 2 2 3 3 4 4 5 5 6 6 3 2 To host CXO6234A Table 2–5 Key to Figure 2–8 Cabling for Dual-Redundant Configuration with One Hub using Fibre Channel Copper Support Item Description 1 Dual Controller 2 9-p
2–22 HSG80 User’s Guide 3. Connect the Fibre Channel cable from Port 1 on controller A to Port 9 on hub 1. Repeat this step to connect the second cable from Port 1 on controller B to Port 8 on hub 1. 4. Connect another Fibre Channel cable from Port 2 on controller A to Port 1 on hub 2. Repeat this step to connect the final cable from Port 2 on controller B to Port 2 on hub 2. 5. Connect each hub to their respective host according to the instructions supplied in the Getting Started manual. 6.
Configuring an HSG80 Array Controller 2–23 Table 2–6 Key to Figure 2–9 Cabling for Dual-Redundant Configuration with One Hub using Fibre Channel Optical Support Item Description Part No. 1 Dual Controller — 2 12-Port Fibre Channel HUB DHGGA-CA 3 .
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.
3–2 HSG80 User’s Guide 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.
Creating Storagesets Figure 3–1 Units Created from Storagesets, Partitions, and Drives Unit Unit Mirrorset Unit Stripeset Partitioned storageset RAIDset Unit Striped mirrorset Disk drives Unit Partitioned disk drive Unit CXO5368B Table 3–1 Controller Limitations for RAIDsets RAIDset Type Limit Total number of RAID5 Total number of RAID5 + RAID1 Total number of RAID5 + RAID1 + RAID0 20 30 45 3–3
3–4 HSG80 User’s Guide 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.
Creating Storagesets 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 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–2.
3–6 HSG80 User’s Guide Figure 3–2 A Typical Storageset Profile Type of storageset _____ Mirrorset __✔_ RAIDset _____ Stripeset _____ Striped Mirrorset Storageset Name ... accept default values Disk Drives............ DISK10300, DISK20300, DIS30300 Unit Number.........
Creating Storagesets 3–7 Determining Storage Requirements Start the planning process by determining your storage requirements.
3–8 HSG80 User’s Guide Choosing a Storageset Type Different applications may have different storage requirements, so you will probably want to configure more than one kind of storageset in your subsystem. All of the storagesets described in this book implement RAID (Redundant Array of Independent Disks) technology. 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.
Creating Storagesets 3–9 called “chunks.” These chunks are then “striped” across the disk drives in the storageset, thereby allowing several disk drives to participate in one I/O request to handle several I/O requests simultaneously. For example, in a three-member stripeset that contains disk drives 10000, 20000, and 30000, the first chunk of an I/O request is written to 10000, the second to 20000, the third to 30000, the fourth to 10000, and so forth until all of the data has been written to the drives.
3–10 HSG80 User’s Guide Considerations for Planning a Stripeset Keep the following points in mind as you plan your stripesets: n n n A controller can support up to 45 storagesets, consisting of stripesets, mirrorsets and RAIDsets (refer to Table 3–1). Reporting methods and size limitations prevent certain operating systems from working with large stripesets. See the HSG80 Array Controller ACS Version 8.
Creating Storagesets Figure 3–4 1 3–11 Distribute Members across Ports 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 n n Stripesets contain between 2 and 24 members.
3–12 HSG80 User’s Guide n n Applications that make requests for small amounts of sequentially-located data Applications that make synchronous random requests for small amounts of data By spreading the traffic evenly across the buses, you will ensure that no bus handles the majority of data to the storageset. Using Mirrorsets to Ensure Availability Mirrorsets use redundancy to ensure availability, as illustrated in Figure 3–5. For each primary disk drive, there is at least one mirror disk drive.
Creating Storagesets n n n n 3–13 You can configure up to 30 mirrorsets per controller or pair of dualredundant controllers. Each mirrorset contains a minimum of one and a maximum of six members. A write-back cache module is required for mirrorsets, but writeback cache need not be enabled for the mirrorset to function properly. Both write-back cache modules must be the same size.
3–14 HSG80 User’s Guide n n n n Mirrorset units are set to WRITEBACK_CACHE by default which increases a unit’s performance. 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. 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 waste 5 GB of capacity on each 9 GB member.
Creating Storagesets 3–15 Using RAIDsets to Increase Performance and Availability RAIDsets are enhanced stripesets—they use striping to increase I/O performance and distributed-parity data to ensure data availability. Figure 3–7 illustrates the concept of RAIDsets and parity data.
3–16 HSG80 User’s Guide The relationship between the chunk size and the average request size determines if striping maximizes the request rate or the data-transfer rates. You can set the chunk size or let the controller set it automatically. See “Chunk Size,” page 3–47, for information about setting the chunk size.
Creating Storagesets n n n 3–17 High read request rates Inquiry-type transaction processing RAIDsets are not particularly well-suited for the following: n n n n n Write-intensive applications Applications that require high data transfer capacity High-speed data collection Database applications in which fields are continually updated Transaction processing Using Striped Mirrorsets for Highest Performance and Availability As illustrated in Figure 3–8, striped mirrorsets are simply stripesets whose memb
3–18 HSG80 User’s Guide require any more disk drives than mirrorsets, this storageset is an excellent choice for data that warrants mirroring. 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–12.
Creating Storagesets 3–19 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–20 HSG80 User’s Guide Figure 3–9 CLONE Steps for Duplicating Unit Members Unit Unit Temporary mirrorset Disk10300 Disk10300 New member Unit Temporary mirrorset Unit Copy Disk10300 Disk10300 New member Clone Unit Clone of Disk10300 CXO5510A 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. 2. Start CLONE using the following command: RUN CLONE 3.
Creating Storagesets 3–21 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. Example This example shows the commands you would use to clone storage unit D98. The clone command terminates after it creates storage unit D99, a clone or copy of D98.
3–22 HSG80 User’s Guide DEVICES AVAILABLE FOR CLONE TARGETS: DISK20300 (SIZE=832317) DISK30100 (SIZE=832317) USE AVAILABLE DEVICE DISK10400(SIZE=832317) FOR MEMBER DISK10000(SIZE=832317) (Y,N) [Y] ? Y MIRROR DISK10000 C_MB SET C_MB NOPOLICY SET C_MB MEMBERS=2 SET C_MB REPLACE=DISK10400 COPY IN PROGRESS FOR EACH NEW MEMBER. PLEASE BE PATIENT... . .
Creating Storagesets 3–23 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–51, and “Saving Configuration Information in Dual-Redundant Configurations,” page 3–52, for more information.
3–24 HSG80 User’s Guide the SAVE_CONFIGURATION switch. Use the following command for each: INITIALIZE DISK nnn SAVE_CONFIGURATION Saving Subsystem Configuration Information to a Storageset You can save your subsystem configuration information to a storageset. The configuration information is duplicated on every disk that is a member of the storageset.
Creating Storagesets 3–25 The following example shows sample devices with the SAVE_CONFIGURATION switch enabled: $ SHOW DEVICES FULL Name Type Port Targ Lun Used by -----------------------------------------------------------------------------DISK10000 disk 1 0 0 S2 DEC Switches: RZ28M (C) DEC 1003 NOTRANSPORTABLE TRANSFER_RATE_REQUESTED = 20MHZ (synchronous 10.
3–26 HSG80 User’s Guide Controller and Port Worldwide Names (Node IDs) A worldwide name (node ID) is a unique 64-bit number assigned to a subsystem by the Institute of Electrical and Electronics Engineers (IEEE) and set by DIGITAL manufacturing prior to shipping. The worldwide name assigned to a subsystem never changes. Each subsystem’s worldwide name ends in zero, for example 5000-1FE1-FF0C-EE00. The controller port ID numbers are derived from the worldwide name.
Creating Storagesets 3–27 Unit World Wide Names (LUN IDs) In addition, each unit has its own world wide name, or LUN ID. This is a unique, 128-bit value that the controller assigns at the time of unit initialization. It cannot be altered by the user but does change when the unit is re-initialized. Use the SHOW command to list the LUN ID. Caution Each subsystem has its own unique worldwide name (node ID).
3–28 HSG80 User’s Guide Assigning Unit Numbers for Host Access to Storagesets You will need to assign a unit number to each storageset, single disk unit, or storage device that you want your host to know about in your subsystem. The host uses these numbers to indicate the source or target for every I/O request it sends to a controller. Each unit number contains the following: n n A letter that indicates the kind of devices in the storage unit.
Creating Storagesets 3–29 Assigning Unit Numbers in Multiple Bus Failover Mode In multiple bus failover mode, the range of assignable units, which are accessible from any port on the subsystem, is 0-199. Hosts obtain units by reserving the unit for sole access. This is done on a first-available basis. Figure 3–11 illustrates the controller port ID and unit numbers in multiple bus failover mode.
3–30 HSG80 User’s Guide Figure 3–12 LUN Presentation Using Unit Offset on a Per-Host Basis Controller Units HOST 1 on Port 1 Dev Offset: 0 HOST 2 on Port 1 Dev Offset: 20 D0 LUN 0 D1 LUN 1 D2 LUN 2 D3 LUN 3 D20 LUN 20 LUN 0 D21 LUN 21 LUN 1 HOST 3 on Port 2 Dev Offset: 100 D100 LUN 0 D101 LUN 1 D102 LUN 2 D130 LUN 30 D131 LUN 31 CXO6455A Assigning Access Paths The HSG80 subsystem allows the user to specify unit access privileges to limit host access.
Creating Storagesets 3–31 By default, host access is set to ALL. If you wish to have the unit access limited, you must first disable access to ALL, then set it to a specified host access path. You can define a unit’s access privileges with the ADD command. These access privileges can be changed using the SET command. See Appendix B, “CLI Commands,” for more information about these commands.
3–32 HSG80 User’s Guide 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–13. 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. Figure 3–13 Storageset Map To create a storageset map: 1.
Creating Storagesets 3–33 2. Establish a local or remote connection to one of the controllers in your subsystem. 3. Show the devices that are assigned to the controller. Use the following command: SHOW DEVICES 4. Locate each device assigned to the controller and record its location on your copy of the cabinet template. Use the following command: LOCATE device_name The LOCATE command causes the device’s LED to flash continuously. 5.
3–34 HSG80 User’s Guide Note The controller operates with BA370 rack-mountable enclosures that are assigned ID numbers 0, 2, and 3. These ID numbers are set through 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. Place one space between the port number, target number, and the twodigit LUN number when entering the PTL address. An example of a PTL address is shown below.
Target numbers 1 2 3 10100 10200 10300 1 20000 20100 20200 20300 2 30000 30100 30200 30300 3 40000 40100 40200 40300 4 50000 50100 50200 50300 5 60000 60100 60200 60300 6 9 10 11 10900 11000 11100 1 20800 20900 21000 21100 2 30800 30900 31000 31100 3 40800 40900 41000 41100 4 50800 50900 51000 51100 5 60800 60900 61000 61100 6 PVA 2 8 EMU 14 15 11200 11300 11400 11500 1 21200 21300 21400 21500 2 31200 31300 31400 31500 3 4120
3–36 HSG80 User’s Guide In Figure 3–15, the controller addresses DISK30800 through device port 3, target 08, LUN 00. This PTL location indicates the pathway the controller uses to address a disk drive (device) in the subsystem. It also indicates the device name. The controller uses the PTL location to name each device that you add to your subsystem with StorageWorks Command Console or the CONFIG utility. (Factory-installed devices are added with the CONFIG utility.
Creating Storagesets 3–37 Planning Partitions Use partitions to divide a storageset or disk drive into smaller pieces, which can each be presented to the host as its own storage unit. Figure 3–17 shows the conceptual effects of partitioning a single-disk unit. Figure 3–17 Partitioning a Single-Disk Unit Partition 1 Partition 2 Partition 3 CXO-5316A-MC You can create up to eight partitions per disk drive, RAIDset, mirrorset, stripeset, or striped mirrorset.
3–38 HSG80 User’s Guide Guidelines for Partitioning Storagesets and Disk Drives Keep these points in mind as you plan your partitions: n n n n n n You can create up to eight partitions per storageset or disk drive. All of the partitions on the same storageset or disk drive must be addressed through the same controller port. This ensures a transparent failover of devices should one of the dual-redundant controllers fail. Partitions cannot be combined into storagesets.
Creating Storagesets 3–39 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”: n n n n 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–40 HSG80 User’s Guide RAIDset Switches You can enable the following switches to control how a RAIDset behaves to ensure data availability: n n n Replacement policy Reconstruction policy Membership Replacement Policy Specify a replacement policy to determine how the controller replaces a failed disk drive: n n n 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 ope
Creating Storagesets 3–41 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: n n NOREDUCED (default) indicates to the controller that all of the disk drives are present for a RAIDset. REDUCED lets you add a RAIDset that is missing one of its members. For example, if you dropped or destroyed a disk drive while moving a RAIDset, you could still add it to the subsystem by using this switch.
3–42 HSG80 User’s Guide Mirrorset Switches You can enable the following switches to control how a mirrorset behaves to ensure data availability: n n n Replacement policy Copy speed Read source Replacement Policy Specify a replacement policy to determine how the controller replaces a failed disk drive: n n n 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 operation
Creating Storagesets 3–43 Read Source Specify the read source to determine how the controller reads data from the members of a mirrorset: n n n READ_SOURCE=LEAST_BUSY (default) forces the controller to read data from the “normal” or operational member that has the least-busy work queue. If multiple disks have equally short queues, the controller queries normal local disks for each read request as it would when READ_SOURCE=ROUND_ROBIN is specified.
3–44 HSG80 User’s Guide Device Switches When you add a disk drive or other storage device to your subsystem, you can enable the following switches: n n Transportability Transfer rate Transportability Indicate whether a disk drive is transportable when you add it to your subsystem: n NOTRANSPORTABLE disk drives (default) are marked with StorageWorks-exclusive metadata. This metadata supports the error-detection and recovery methods that the controller uses to ensure data availability.
Creating Storagesets 3–45 TRANSPORTABLE is especially useful for moving a disk drive from a workstation into your StorageWorks subsystem. When you add a disk drive as transportable, you can configure it as a singledisk unit and access the data that was previously saved on it. Transportable devices have these characteristics: n n n n Can be interchanged with any SCSI interface that does not use the device metadata, for example, a PC. Cannot have write-back caching enabled.
3–46 HSG80 User’s Guide Device Transfer Rate Specify a transfer rate that the controller uses to communicate with the device. Use one of these switches to limit the transfer rate to accommodate long cables between the controller and a device, such as a tape library.
Creating Storagesets 3–47 Initialize Switches You can enable the following kinds of switches to affect the format of a disk drive or storageset: n n n 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–48 HSG80 User’s Guide 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–18.
Creating Storagesets 3–49 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. This concept is shown in Figure 3–19.
3–50 HSG80 User’s Guide Maximum Chunk Size for RAIDsets Do not exceed the chunk sizes shown in Table 3–3 for a RAIDset. (The maximum chunk size is derived by 2048/(d – 1) where d is the number of disk drives in the RAIDset.
Creating Storagesets n n 3–51 All configuration information normally saved when you restart your controller except, the controller serial number, product ID number, vendor ID number, and any manufacturing fault information.
3–52 HSG80 User’s Guide n When you replace a controller, make sure the replacement controller does not contain any configuration data. If the controller is not new, use the CONFIGURATION RESET command to purge any existing configuration. If you do not take this precaution, you can lose configuration data if non-volatile memory changes.
Creating Storagesets n n 3–53 DESTROY (default) overwrites the user data and forced-error metadata on a disk drive when it is initialized. NODESTROY preserves the user data and forced-error metadata when a disk drive is initialized. Use NODESTROY to create a single-disk unit from any disk drive that has been used as a member of a mirrorset. See the REDUCED command in the Appendix B, “CLI Commands,” for information on removing disk drives from a mirrorset.
3–54 HSG80 User’s Guide Unit Switches You can enable the Unit switches listed in Table 3–4 for the listed storagesets and devices.
Creating Storagesets 3–55 Configuring Storagesets with CLI Commands One method of configuring storagesets is manual configuration. This method allows you the most flexibility in defining and naming storagesets. See Appendix B, “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.
3–56 HSG80 User’s Guide 3. 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, the default values are applied. ADD UNIT unit-number stripeset-name switch 4. Verify the stripeset configuration and switches. Use the following command: SHOW stripeset-name 5. Verify the unit configuration and switches.
Creating Storagesets 3–57 2. Initialize the mirrorset. If you want to set any Initialize switches, you must do so in this step. Use the following command: INITIALIZE mirrorset-name switch 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, the default values are applied. Use the following command: ADD UNIT unit-number mirrorset-name switch 4.
3–58 HSG80 User’s Guide Use the following command to create a RAIDset: ADD RAIDSET RAIDset-name DISK nnnnn DISK nnnnn DISK nnnnn switch 2. Initialize the RAIDset. Optional: If you want to set the Initialize switches, you must do so in this step. Use the following command: INITIALIZE RAIDset-name switch Note It is recommended that you allow initial reconstruct to complete before allowing I/O to the RAIDset. Not doing so may generate forced errors at the host level.
Creating Storagesets 3–59 Configuring a Striped Mirrorset See Chapter 3, “Creating Storagesets,” for information about creating a profile and understanding the switches you can set for this kind of storage unit. To configure a striped mirrorset: 1. Create—but do not initialize—at least two mirrorsets. 2. Create a stripeset and specify the mirrorsets it contains. Use the following command: ADD STRIPESET mirrorset_1 mirrorset_2 3. Initialize the stripeset.
3–60 HSG80 User’s Guide Example The following example shows the commands you would use to create Stripe1, a three-member 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 For more detailed information on configuring a
Creating Storagesets 3–61 Example The following example shows the commands you would use to configure DISK10000 as a single-disk unit. ADD DISK DISK10000 1 0 0 ADD UNIT D101 DISK10000 SHOW DEVICES See Appendix B, “CLI Commands,” for further information on these switches and values. Partitioning a Storageset or Disk Drive See “Planning Partitions,” page 3–37, for details about partitioning a storage unit. To partition a storageset or disk drive: 1.
3–62 HSG80 User’s Guide The partition number appears in the first column, followed by the size and starting block of each partition. 5. Present each partition to the host by giving it a unit number the host can recognize. (You can skip this step until you are ready to put the partitions online.) Optionally, you can append Unit switch values. If you do not specify switch values, the default values are applied.
Creating Storagesets 3–63 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 Size Starting Block 1 1915 (0.98 MB) 0 2 1915 (0.98 MB) 1920 3 1915 (0.98 MB) 3840 4 2371 (1.21 MB) 5760 . . . Used by D1 D2 D3 D4 Appendix B, “CLI Commands,” contains more information on partitioning a storageset or disk drive.
3–64 HSG80 User’s Guide 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. However, you can delete disks in the spareset if you need to use them elsewhere in your StorageWorks subsystem. To remove a disk drive from the spareset: 1.
Creating Storagesets 3–65 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. If initialization fails, the disk drive remains in the failedset until you manually delete it from the failedset.
3–66 HSG80 User’s Guide Example The following example shows the commands you would use to delete Stripe1, a three-member stripeset that is comprised of DISK10000, DISK20000, and DISK30000. SHOW STORAGESETS Name STRIPE1 Storageset stripeset Uses DISK10000 DISK20000 DISK30000 Used by D100 DELETE D100 DELETE STRIPE1 SHOW STORAGESETS 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.
Creating Storagesets 3–67 Changing Device Switches Use the SET command to change the device switches. For example, the following command enables DISK10000 to be used in a nonStorageWorks environment: SET DISK10000 TRANSPORTABLE The TRANSPORTABLE switch cannot be changed for a disk if the disk is part of an upper-level container. Additionally, the disk cannot be configured as a unit if it is to be used as indicated in this example.
3–68 HSG80 User’s Guide Configuring with the Command Console LUN The Command Console LUN (CCL) is a type of LUN that allows you to communicate with the controller from the host using StorageWorks Command Console (SWCC) or CLI commands instead of using the maintenance port cable.
Creating Storagesets 3–69 To turn it off, use the following command: SET THIS_CONTROLLER NOCOMMAND_CONSOLE_LUN Caution Disabling the CCL while SWCC is running may result in loss of connection for the StorageWorks Command Console. Turn off SWCC before issuing the command. 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.
3–70 HSG80 User’s Guide SCSI-3 Mode In SCSI-3 mode, a CCL will appear at LUN 0 of each unit offset. Multiple-Bus Failover If you are in multiple-bus failover mode, all ports will be able to see and access the CCLs. As a result, all hosts will have access to each CCL, and they will appear to the host as array controllers. Transparent Failover If you are in transparent failover mode, each CCL will be accessible from the port that has the unit offset enabled.
Creating Storagesets 3–71 SCSI-3 Mode The CCL will appear at the default unit offset of each port. Because the default unit offset is 0 for Port 1 and 100 for Port 2, the CCL will be at LUN 0 on Port 1 and LUN 100 on Port 2. Note Lun 100 on Port 2 appears as LUN 0 to its hosts.
3–72 HSG80 User’s Guide Moving Storagesets You can move a storageset from one subsystem to another without destroying its data as shown in Figure 3–20. You also can follow the steps in this section to move a storageset to a new location within the same subsystem. Caution Move only normal storagesets. Do not move storagesets that are reconstructing or reduced, or data corruption will result.
Creating Storagesets 3–73 1. Show the details for the storageset you want to move. Use the following command: SHOW storageset-name 2. 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. Use the following command: LOCATE disk-name To cancel the locate command, enter the following: LOCATE CANCEL 3.
3–74 HSG80 User’s Guide 9. Represent the storageset to the host by giving it a unit number the host can recognize. You can use the original unit number or create a new one. Use the following command: ADD UNIT unit-number storageset-name Example The following example moves unit D100 to another cabinet. D100 is the RAIDset RAID99 that is comprised of members DISK10000, DISK20000, and DISK30000.
Creating Storagesets 3–75 Example The following example moves 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.) DELETE D100 DELETE R3 DELETE DISK10000 DELETE DISK30000 DELETE DISK40000 (...move disk drives to their new location...
4–1 CHAPTER 4 Troubleshooting This chapter provides guidelines for troubleshooting the controller, cache module, and external cache battery (ECB). It also describes the utilities and exercisers that you can use to aid in troubleshooting these components. See the appendixes for a list of LEDs and event codes. See the documentation that accompanied the enclosure for information on troubleshooting its hardware, such as the power supplies, cooling fans, and environmental monitoring unit (EMU).
4–2 HSG80 User’s Guide Troubleshooting Checklist The following checklist provides a general procedure for diagnosing the controller and its supporting modules. If you follow this checklist, you’ll be able to identify many of the problems that occur in a typical installation. When you’ve identified the problem, use Table 4–1 to confirm your diagnosis and fix the problem.
Troubleshooting 4–3 7. Check the status of the devices with the following command: SHOW DEVICES FULL Look for errors such as “misconfigured device” or “No device at this PTL.” If a device reports misconfigured or missing, check its status with the following command: SHOW device-name 8. Check the status of the storagesets with the following command: SHOW STORAGESETS FULL Ensure that all storagesets are normal (or normalizing if it’s a RAIDset or mirrorset).
4–4 HSG80 User’s Guide Troubleshooting Table Use the troubleshooting checklist that begins on page 4–2 to find a symptom, then use this table to verify and fix the problem. Table 4–1 Troubleshooting Table Symptom Reset button not lit Possible Cause Investigation Remedy No power to subsystem. Check power to Replace cord or AC subsystem and power input power module. supplies on controller’s shelf. Ensure that all cooling fans are installed.
Troubleshooting Table 4–1 4–5 Troubleshooting Table (Continued) Symptom Cannot set failover to create dual-redundant configuration. Possible Cause Incorrect command syntax. Investigation See Appendix B, “CLI Commands,” for the SET FAILOVER command. Remedy Use the correct command syntax. Different software Check software versions on controllers. versions on both controllers. Update one or both controllers so that both controllers are using the same software version. Incompatible hardware.
4–6 HSG80 User’s Guide Table 4–1 Troubleshooting Table (Continued) Symptom Nonmirrored cache; controller reports failed DIMM in cache module A or B. Mirrored cache; “this controller” reports DIMM 1 or 2 failed in cache module A or B. Mirrored cache; “this controller”reports DIMM 3 or 4 failed in cache module A or B. Possible Cause Investigation Remedy Improperly installed DIMM. Remove cache module Reseat DIMM (see and ensure that DIMM Figure 5–8 on page is fully seated in its slot. 5–44).
Troubleshooting Table 4–1 4–7 Troubleshooting Table (Continued) Symptom Mirrored cache; controller reports cache or mirrored cache has failed. Possible Cause Investigation Remedy Primary data and its mirrored copy data are not identical. SHOW THIS_CONTROLLER indicates that the cache or mirrored cache has failed. Enter the SHUTDOWN command on controllers that report the problem. (This command flushes the contents of cache to synchronize its primary and mirrored data.
4–8 HSG80 User’s Guide Table 4–1 Troubleshooting Table (Continued) Symptom Invalid cache Possible Cause Investigation Mirrored-cache mode discrepancy. This may occur after you’ve installed a new controller. Its existing cache module is set for mirrored caching, but the new controller is set for unmirrored caching. (It may also occur if the new controller is set for mirrored caching but its existing cache module is not.) SHOW THIS CONTROLLER indicates “invalid cache.
Troubleshooting Table 4–1 4–9 Troubleshooting Table (Continued) Symptom Cannot add device Cannot configure storagesets Possible Cause Investigation Remedy Illegal device. Replace device. See product-specific release notes that accompanied the software release for the most recent list of supported devices. Device not properly installed in shelf. Check that SBB is fully Firmly press SBB into seated. slot. Failed device. Check for presence of device LEDs.
4–10 HSG80 User’s Guide Table 4–1 Troubleshooting Table (Continued) Symptom Possible Cause Can’t assign unit number Incorrect command to storageset. syntax. Incorrect SCSI target ID numbers set for controller that accesses desired unit. (First number of unit number must be one of the SCSI target ID numbers for the controller.) Investigation Remedy See the Appendix B, “CLI Commands,” for correct syntax. Reassign the unit number with the correct syntax.
Troubleshooting Table 4–1 4–11 Troubleshooting Table (Continued) Symptom Possible Cause Investigation Remedy Host’s log file or maintenance terminal indicates that a forced error occurred when the controller was reconstructing a RAIDset or mirrorset Unrecoverable read errors may have occurred when controller was reconstructing the storageset. Errors occur if another member fails while the controller is reconstructing the storageset.
4–12 HSG80 User’s Guide Figure 4–1 Troubleshooting: Host Cannot Access Unit Start CLI: SHOW this Controller loop up? Refer to Hub User's Guide for information on how to determine this.
Troubleshooting 4–13 Figure 4–1 Troubleshooting: Host Cannot Access Unit (continued) A Driver loaded? Y Event log errors for adapters? N B CLI: CLEAR_ERRORS INVALID_CACHE N Y CLI: SHOW this • Shutdown • Re-seat GLM • Re-seat adapter • Check cables or add loopback • Go to Start NOTE: If this happens more than two times, there may be PCI restrictions on your adapter. Refer to your adapter's readme file for specifics.
4–14 HSG80 User’s Guide Significant Event Reporting The controller’s fault-management software reports information about significant events that occur. These events are reported via the: n n n Maintenance terminal Host error log Operator control panel (OCP) Some events cause controller operation to terminate; others allow the controller to remain operable. Each of these two instances are detailed in the following sections.
Troubleshooting 4–15 Last Failure Reporting Last Failures are displayed on the maintenance terminal using %LFL formatting. The example below details an occurrence of a Last Failure report: %LFL--HSG> --13-JAN-1946 04:39:45 (time not set)-- Last Failure Code: 20090010 Power On Time: 0.Years, 14.Days, 19.Hours, 58.Minutes, 42.
4–16 HSG80 User’s Guide Spontaneous Event Log Spontaneous event logs are displayed on the maintenance terminal using %EVL formatting, as illustrated in the following examples: %EVL--HSG> --13-JAN-1946 04:32:47 (time not set)-- Instance Code: 0102030A (not yet reported to host) Template: 1.(01) Power On Time: 0.Years, 14.Days, 19.Hours, 58.Minutes, 43.
Troubleshooting 4–17 Fault Management Utility The Fault Management Utility (FMU) provides a limited interface to the controller’s fault-management software. Use FMU to: n n n Display the last-failure and memory-system-failure entries that the fault-management software stores in the controller’s non-volatile memory. Translate many of the code values contained in event messages.
4–18 HSG80 User’s Guide n FULL displays additional information, such as the I960 stack and hardware component register sets (for example, the memory controller, FX, host port, and device ports, and so on). 4. Exit FMU with the following command: EXIT Example The following example shows a last-failure entry. The Informational Report—the lower half of the entry—contains the instance code, reporting component, and so forth that you can translate with FMU to learn more about the event.
Troubleshooting 4–19 3. Show one or more of the entries with the following command: DESCRIBE code_type code# where code_type is one of those listed in Table 4–2 and code# is the alpha-numeric value displayed in the entry. The code types marked with an asterisk (*) require multiple code numbers.
4–20 HSG80 User’s Guide Controlling the Display of Significant Events and Failures You can control how the fault-management software displays significant events and failures with FMU’s SET command. Table 4–3 describes various SET commands that you can enter while running FMU. These commands remain in effect only as long as the current FMU session remains active, unless you enter the PERMANENT qualifier—the last entry in Table 4–3.
Troubleshooting Table 4–3 4–21 FMU SET Commands (Continued) Command Result SET PROMPT SET NOPROMPT enable and disable the display of the CLI prompt string following the log identifier “%EVL,” or “%LFL,” or “%FLL.” This command is useful if the CLI prompt string is used to identify the controllers in a dual-redundant configuration (see Appendix B, “CLI Commands,” for instructions to set the CLI command string for a controller).
4–22 HSG80 User’s Guide Table 4–3 FMU SET Commands (Continued) Command SET FAULT_LED_LOGGING SET NOFAULT_LED_LOGGING Result enable and disable the solid fault LED event log display on the local terminal. Preceded by “%FLL.” By default, logging is enabled (SET FAULT_LED_LOGGING). When enabled, and a solid fault pattern is displayed in the OCP LEDs, the fault pattern and its meaning are displayed on the maintenance terminal.
Troubleshooting 4–23 Using VTDPY to Check for Communication Problems Use the virtual terminal display (VTDPY) utility to get information about the following communications: n n n Communication between the controller and its hosts Communication between the controller and the devices in the subsystem The state and I/O activity of the logical units, devices, and device ports in the subsystem Use the following steps to run VTDPY: 1. Connect a terminal to the controller.
4–24 HSG80 User’s Guide You may abbreviate the commands to the minimum number of characters necessary to identify the command. Enter a question mark (?) after a partial command to see the values that can follow the supplied command. For example, if you enter DISP ?, the utility will list CACHE, DEFAULT, and so forth. (Separate “DISP” and “?” with a space.) Upon successfully executing a command—other than HELP— VTDPY exits command mode.
Troubleshooting 4–25 Figure 4–3 Regions on the Device Display VTDPY>DISPLAY DEVICE 67% I/D Target 111111 0123456789012345 P1 hH PDD o2 hH DDD r3 ????hH t4 hH DDD 5 P hH 6 DDD hH Port 1 2 3 4 5 6 Rq/S 0 0 0 0 0 0 RdKB/S 0 0 0 0 0 0 PTL P1120 D1130 D1140 D2120 D2130 D2150 ?3020 ?3030 ?3040 ?3050 D4090 D4100 D4110 P5030 D6010 D6020 D6030 WrKB/S 0 0 0 0 0 0 CR 0 0 0 0 0 0 ASWF A^ A^ A^ A^ A^ a^ ^F ^F ^F ^F A^ A^ A^ A^ A^ A^ A^ BR 0 0 0 0 0 0 S/N: ZG64100176 SW: v7.0 HW: CX-02 99.
4–26 HSG80 User’s Guide Table 4–5 Device Map Columns (Continued) Column Contents P = passthrough device ? = unknown device type = no device at this port/target location Checking Device Status and I/O Activity The device status region of the device display (upper right) shows the name and I/O characteristics for all of the devices that the controller recognizes. Table 4–6 lists the heading and contents for each column of the device status region.
Troubleshooting 4–27 Table 4–6 Device Status Columns (Continued) Column Contents = unknown spindle state W Write-protection state of the device. For disk drives, a W in this column indicates that the device is hardware write-protected. This column is blank for other kinds of devices. F Fault state of the device. An F in this column indicates an unrecoverable device fault. If this field is set, the device fault LED should also be lit.
4–28 HSG80 User’s Guide Checking Device-Port Status and I/O Activity The device-port status region of the device display (lower left) shows the I/O characteristics for the controller’s device ports. Table 4–7 lists the heading and contents for each column of the device-port status region. Table 4–7 Device-Port Status Columns Column Contents Port SCSI device ports 1 through 6. Rq/S Average request rate for the port during the last update interval.
Troubleshooting 4–29 Checking Unit Status and I/O Activity Use the cache display to see the status and I/O activity for the logical units configured on the controller (see Figure 4–4). Table 4–8 lists the heading and contents for each column of the device status region. Figure 4–4 Unit Status on the Cache Display VTDPY> DISPLAY CACHE 66% I/D Unit P0300 D0303 D0304 P0400 P0401 D0402 ASWC o o^ b x^ b S/N: ZG64100176 SW: v7.0 HW: CX-02 Hit 99.
4–30 HSG80 User’s Guide Table 4–8 Unit Status Columns (Continued) Column Contents x = online. Host may access this unit through “other controller.” = unknown availability S Spindle state of the device: ^ = disk spinning at correct speed; tape loaded > = disk spinning up; tape loading < = disk spinning down; tape unloading v = disk not spinning; tape unloaded = unknown spindle state W Write-protection state. For disk drives, a W in this column indicates that the device is hardware writeprotected.
Troubleshooting 4–31 Table 4–8 Unit Status Columns (Continued) Column Contents x = online. Host may access this unit through “other controller.” = unknown availability S Spindle state of the device: ^ = disk spinning at correct speed; tape loaded > = disk spinning up; tape loading < = disk spinning down; tape unloading v = disk not spinning; tape unloaded = unknown spindle state W Write-protection state. For disk drives, a W in this column indicates that the device is hardware writeprotected.
4–32 HSG80 User’s Guide Table 4–8 Unit Status Columns (Continued) Column Contents HT% Cache-hit percentage for data transferred between the host and the unit. PH% Partial cache-hit percentage for data transferred between the host and the unit. MS% Cache-miss percentage for data transferred between the host and the unit. Purge Number of blocks purged from the cache during the last update interval. BlChd Number of blocks added to the cache during the last update interval.
Troubleshooting 4–33 Figure 4–5 Fibre Channel Host Status Display FIBRE CHANNEL HOST STATUS DISPLAY ********* KNOWN ## NAME BB 00 ASSIGN 0 01 !NEWCON47 0 HOSTS ********** FrSz ID/ALPA P S 2048 01 1F 2048 81 2N ******* PORT 1 ******* Topology : LOOP Current Status : STNDBY Current ID/ALPA : Tachyon Status : 0 Queue Depth : 0 Busy/QFull Rsp : 0 LINK ERROR COUNTERS Link Downs : 30 Soft Inits : 14 Hard Inits : 0 Loss of Signals : 0 Bad Rx Chars : 243 Loss of Syncs : 0 Link Fails : 0 Received EOFa : 0 Genera
4–34 HSG80 User’s Guide The following tables detail the remaining portions of the Fibre Channel Host Status Display. Table 4–10 includes the labels that report the status of ports one and two, and Table 4–11 describes the Link Error Counters. Table 4–10 Fibre Channel Host Status Display- Port Status Field Label Description Topology LOOP OFFLNE Current Status DOWN LOOP STNDBY Current ID/ALPA Controller ID Tachyon Status This denotes the current state of the Tachyon, or Fibre Channel control chip.
Troubleshooting 4–35 Table 4–11 Fibre Channel Host Status Display- Link Error Counters (Continued) Field Label Description Bad Rx Chars This field represents the number of times the 8B/10B decode detected an invalid 10-bit code. FC-PH denotes this value as “Invalid Transmission Word during frame reception.” This field may be non-zero after initialization. After initialization, the host should read this value to determine the correct starting value for this error count.
4–36 HSG80 User’s Guide Tachyon Status The number that appears in the Tachyon Status field represents the current state of the Tachyon, or Fibre Channel control chip. It consists of a two-digit hex number, the first of which is explained in Figure 4–12. The second digit is outlined in Figure 4–13. Refer to the Tachyon user’s manual for a more detailed explanation of the Tachyon definitions.
Troubleshooting 4–37 Checking for Disk-Drive Problems Use the disk inline exerciser (DILX) to check the data-transfer capability of disk drives. DILX generates intense read/write loads to the disk drive while monitoring the drive’s performance and status. You may run DILX on as many disk drives as you’d like, but because this utility creates substantial I/O loads on the controller, DIGITAL recommends that you stop host-based I/O during the test.
4–38 HSG80 User’s Guide 7. If you want to test more than one disk drive, enter the appropriate unit numbers when prompted. Otherwise, enter “n” to start the test. Use the control sequences listed in Table 4–14 to control DILX during the test.
Troubleshooting 4–39 Table 4–15 Data Patterns for Phase 1: Write Test Pattern Pattern in Hexadecimal Numbers 1 0000 2 8B8B 3 3333 4 3091 5 0001, 0003, 0007, 000F, 001F, 003F, 007F, 00FF, 01FF, 03FF, 07FF, 0FFF, 1FFF, 3FFF, 7FFF 6 FIE, FFFC, FFFC, FFFC, FFE0, FFE0, FFE0, FFE0, FE00, FC00, F800, F000, F000, C000, 8000, 0000 7 0000, 0000, 0000, FFFF, FFFF, FFFF, 0000, 0000, FFFF, FFFF, 0000, FFFF, 0000, FFFF, 0000, FFFF 8 B6D9 9 5555, 5555, 5555, AAAA, AAAA, AAAA, 5555, 5555, AAAA, AAAA, 5
4–40 HSG80 User’s Guide Use the following steps to test the read and write capabilities of a specific disk drive: 1. From a host console, dismount the logical unit that contains the disk drive you want to test. 2. Connect a terminal to the maintenance port of the controller that accesses the disk drive you want to test. 3. Run DILX with the following command: RUN DILX 4. Decline the auto-configure option so that you can specify the disk drive to test.
Troubleshooting 4–41 17. Choose ALL for the data patterns that DILX issues for write requests. 18. Perform the initial write pass. 19. Allow DILX to compare the read and write data. 20. Accept the default percentage of reads and writes that DILX compares. 21. Enter the unit number of the disk drive you want to test. For example, if you want to test D107, enter the number 107. 22.
4–42 HSG80 User’s Guide Running the Controller’s Diagnostic Test During start up, the controller automatically tests its device ports, host port, cache module, and value-added functions. If you’re experiencing intermittent problems with one of these components, you can run the controller’s diagnostic test in a continuous loop, rather than restarting the controller over and over again. Use the following steps to run the controller’s diagnostic test: 1.
5–1 CHAPTER 5 Replacement Procedures This chapter describes the procedures for replacing the controller, cache module, external cache battery (ECB), gigabit link module (GLM), power verification and addressing (PVA) module, I/O module, PCMCIA card, DIMMs, fibre cable or hub, and a failed storageset member. Additionally, there are procedures for shutting down and restarting the subsystem.
5–2 HSG80 User’s Guide Replacing Modules in a Single Controller Configuration Follow the instructions in this section to replace modules in a single controller configuration (see Figure 5–1). If you’re replacing modules in a dual-redundant controller configuration, see “Replacing Modules in a Dual-Redundant Controller Configuration,” page 5–8. To upgrade a single controller configuration to a dual redundant controller configuration, see “Upgrading to a Dual-Redundant Controller Configuration,” page 6–16.
Replacement Procedures 5–3 Replacing the Controller in a Single Controller Configuration Use the following steps in “Removing the Controller in a Single Controller Configuration” and “Installing the Controller in a Single Controller Configuration” to replace the controller. Removing the Controller in a Single Controller Configuration Use the following steps to remove the controller: 1. From the host console, dismount the logical units in the subsystem.
5–4 HSG80 User’s Guide 6. Disconnect the hub cables from the controller. Note One or two hub cables may be attached, depending on the configuration. 7. If connected, disconnect the PC or terminal from the controller’s maintenance port. 8. Disengage both retaining levers and remove the controller, then place the controller into an antistatic bag or onto a grounded antistatic mat.
Replacement Procedures 5–5 6. See “Configuring an HSG80 Array Controller,” page 2–3, to configure the controller. Note If the controller you’re installing was previously used in another subsystem, it will need to be purged of the controller’s old configuration (see “CONFIGURATION RESET,” page B–45). 7. To restore a configuration saved with the SAVE_CONFIGURATION switch, hold button 6 while releasing the reset button. 8.
5–6 HSG80 User’s Guide Replacing the Cache Module in a Single Controller Configuration Use the following steps in “Removing the Cache Module in a Single Controller Configuration” and “Installing the Cache Module in a Single Controller Configuration” to replace the cache module. Removing the Cache Module in a Single Controller Configuration Use the following steps to remove the cache module: 1. From the host console, dismount the logical units in the subsystem.
Replacement Procedures 5–7 Installing the Cache Module in a Single Controller Configuration Use the following steps to install the cache module: Caution ESD can easily damage a cache module. Wear a snug-fitting, grounded ESD wrist strap. Make sure you align the cache module in the appropriate guide rails. If you do not align the cache module correctly, damage to the backplane can occur. 1. Insert the new cache module into its slot and engage its retaining levers.
5–8 HSG80 User’s Guide Replacing Modules in a Dual-Redundant Controller Configuration Follow the instructions in this section to replace modules in a dualredundant controller configuration (see Figure 5–2). If you’re replacing modules in a single controller configuration, see “Replacing Modules in a Single Controller Configuration,” page 5–2.
Replacement Procedures 5–9 Replacing a Controller and Cache Module in a Dual-Redundant Controller Configuration Use the following steps in “Removing a Controller and Cache Module in a Dual-Redundant Controller Configuration” and “Installing a Controller and its Cache Module in a Dual-Redundant Controller Configuration” to replace a controller and its cache module.
5–10 HSG80 User’s Guide 7. Enter option 1, Other controller and cache module, from the Replace or Remove Options menu. FRUTIL displays the following: Slot Designations (front view) [ --- [ -------- EMU --- Controller A ][ ------- ] [ -------- Controller B ------- ] [ Cache Module A ][ --- PVA --- Cache Module B ] ] Remove both the slot A [or B] controller and cache module? Y/N 8. Enter Y(es) and press return. FRUTIL displays the following: Quiescing all device ports. Please wait.
Replacement Procedures 5–11 10. Disengage both retaining levers and remove the “other controller,” then place the controller into an antistatic bag or onto a grounded antistatic mat. Once the controller is removed, FRUTIL displays the following: Remove the slot A [or B] cache module within x minutes, xx seconds. 11. Disengage both retaining levers and partially remove the “other controller’s” cache module—about half way. 12.
5–12 HSG80 User’s Guide Installing a Controller and its Cache Module in a DualRedundant Controller Configuration Use the following steps to install a controller and its cache module. 1. Connect a PC or terminal to the operational controller. The controller to which you’re connected is “this controller”; the controller whose cache module you’re installing is the “other controller.” 2.
Replacement Procedures 5–13 6. Enter Y(es) and press return. FRUTIL displays the following: Quiescing all device ports. Please wait... Device Port 1 quiesced. Device Port 2 quiesced. Device Port 3 quiesced. Device Port 4 quiesced. Device Port 5 quiesced. Device Port 6 quiesced. All device ports quiesced. . . . Perform the following steps: 1. Turn off the battery for the new cache module by pressing the battery’s shut off button for five seconds 2. Connect the battery to the new cache module. 3.
5–14 HSG80 User’s Guide 9. Insert the new cache module into its slot and engage its retaining levers. FRUTIL displays the following: Insert the controller module, without its program card, in slot A [or B] within x minutes, xx seconds. 10. Ensure that the program card is not in the replacement controller and insert the new controller into its slot. Engage its retaining levers.
Replacement Procedures 5–15 13. Hold the reset button while inserting the program card into the new controller. Release the reset button and replace the ESD cover. The controller will restart. 14. See “Configuring an HSG80 Array Controller,” page 2–3, to configure the controller. 15.
5–16 HSG80 User’s Guide 5. Enter N(o). FRUTIL displays the FRUTIL Main menu: FRUTIL Main Menu: 1. Replace or remove a controller or cache module 2. Install a controller or cache module 3. Replace a PVA module 4. Replace an I/O module 5. Exit Enter choice: 1, 2, 3, 4, or 5 -> 6. Enter option 1, Replace or remove a controller or cache module, from the FRUTIL Main menu. FRUTIL displays the Replace or Remove Options menu: Replace or remove Options: 1. Other controller and cache module 2.
Replacement Procedures 5–17 Caution The device ports must quiesce before removing the controller. Failure to allow the ports to quiesce may result in data loss. Quiescing may take several minutes. ESD can easily damage a controller. Wear a snug-fitting, grounded ESD wrist strap. Note A countdown timer allows a total of two minutes to remove the controller. If you exceed two minutes, “this controller” will exit FRUTIL and resume operations. 9. Remove the hub cables from the “other controller.
5–18 HSG80 User’s Guide Installing a Controller in a Dual-Redundant Controller Configuration Use the following steps to install a controller: 1. Connect a PC or terminal to the operational controller’s maintenance port. The controller to which you’re connected is “this controller”; the controller that you’re installing is the “other controller.” 2. Start FRUTIL with the following command: RUN FRUTIL FRUTIL displays the following: Do you intend to replace this controller’s cache battery? Y/N 3.
Replacement Procedures 5–19 6. Enter Y(es) and press return. FRUTIL displays the following: Quiescing all device ports. Please wait... Device Port 1 quiesced. Device Port 2 quiesced. Device Port 3 quiesced. Device Port 4 quiesced. Device Port 5 quiesced. Device Port 6 quiesced. All device ports quiesced. . . . Insert the controller module, without its program card, in slot A [or B] within x minutes, xx seconds. Note A countdown timer allows a total of two minutes to install the controller.
5–20 HSG80 User’s Guide Note If the controller you’re installing was previously used in another subsystem, it will need to be purged of the controller’s old configuration (see “CONFIGURATION RESET,” page B–45). 8. Wait for FRUTIL to terminate and connect the hub cables to the new controller. Note One or two hub cables may be attached, depending on the configuration. 9. To allow the “other controller” to restart, type the following command: RESTART OTHER _CONTROLLER 10.
Replacement Procedures 5–21 Replacing a Cache Module in a Dual-Redundant Controller Configuration Use the following steps in “Removing a Cache Module in a DualRedundant Controller Configuration” and “Installing a Cache Module in a Dual-Redundant Controller Configuration” to replace a cache module. Note The new cache module must contain the same memory configuration as the cache module it’s replacing.
5–22 HSG80 User’s Guide 6. Enter option 1, Replace or remove a controller or cache module, from the FRUTIL Main menu. FRUTIL displays the Replace or Remove Options menu: Replace or remove Options: 1. Other controller and cache module 2. Other controller module 3. Other cache module 4. Exit Enter choice: 1, 2, 3, or 4 -> 7. Enter option 3, Other cache module, from the Replace or Remove Options menu.
Replacement Procedures 5–23 Note A countdown timer allows a total of two minutes to remove the cache module. If you exceed two minutes, “this controller” will exit FRUTIL and resume operations. 9. Disengage both retaining levers and partially remove the “other controller’s” cache module—about half way. 10. Disable the ECB by pressing the battery disable switch until the status light stops blinking—about five seconds.
5–24 HSG80 User’s Guide Installing a Cache Module in a Dual-Redundant Controller Configuration Use the following steps to install a cache module: 1. Connect a PC or terminal to the operational controller’s maintenance port. The controller to which you’re connected is “this controller”; the controller that you’re installing is the “other controller.” 2. Start FRUTIL with the following command: RUN FRUTIL FRUTIL displays the following: Do you intend to replace this controller’s cache battery? Y/N 3.
Replacement Procedures 5–25 6. Enter Y(es) and press return. FRUTIL displays the following: Quiescing all device ports. Please wait... Device Port 1 quiesced. Device Port 2 quiesced. Device Port 3 quiesced. Device Port 4 quiesced. Device Port 5 quiesced. Device Port 6 quiesced. All device ports quiesced. . . . Perform the following steps: 1. Turn off the battery for the new cache module by pressing the battery’s shut off button for five seconds 2. Connect the battery to the new cache module. 3.
5–26 HSG80 User’s Guide 9. Insert the new cache module into its slot and engage its retaining levers. Note In mirrored mode, FRUTIL will initialize the mirrored portion of the new cache module, check for old data on the cache module, and then restart all device ports. After the device ports have been restarted, FRUTIL will test the cache module and the ECB.
Replacement Procedures 5–27 Replacing the External Cache Battery Storage Building Block The ECB SBB can be replaced with cabinet power on or off. A singlebattery ECB SBB is shown in Figure 5–3 and a dual-battery ECB SBB is shown in Figure 5–4.
5–28 HSG80 User’s Guide Replacing the External Cache Battery Storage Building Block With Cabinet Powered On Use the following steps to replace the ECB SSB with the cabinet powered on: Note The procedure for a dual-redundant controller configuration assumes that a single ECB SBB with a dual battery is installed and an empty slot is available for the replacement ECB SBB. If an empty slot is not available, place the new ECB SBB on the top of the enclosure.
Replacement Procedures 5–29 5. Connect the new battery to the unused end of the Y cable attached to cache A [or B] 6. Disconnect the old battery. Do not wait for the new battery’s status light to turn solid green. 7. Press return. FRUTIL displays the following: Updating this battery’s expiration date and deep discharge history. Field Replacement Utility terminated. 8. Disconnect the PC or terminal from the controller’s maintenance port. 9.
5–30 HSG80 User’s Guide When the controllers shut down, their reset buttons and their first three LEDs are lit continuously. This may take several minutes, depending on the amount of data that needs to be flushed from the cache modules. 4. Turn off the power to the subsystem. 5. Insert the new ECB SBB into its slot. Caution The ECB cable has a 12-volt and a 5-volt pin.
Replacement Procedures 5–31 13. In a dual-redundant controller configuration and if the ECB was replaced for both cache modules, connect the PC or terminal to the other controller’s maintenance port. The controller to which you’re now connected is “this controller.” 14. Repeat steps 9 through 12. 15. Remove the old ECB SBB.
5–32 HSG80 User’s Guide Replacing a GLM Use the following steps in “Removing a GLM” and “Installing a GLM” to replace a GLM in a controller. Figure 5–5 shows the location and orientation of the GLMs. Figure 5–5 Location of GLMs in Controller Access door Release lever Port 1 GLM Locking tab Guide holes GLM connector Port 2 GLM CXO6245A Removing a GLM Use the following steps to remove a GLM: 1.
Replacement Procedures 5–33 Caution ESD can easily damage a GLM. Wear a snug-fitting, grounded ESD wrist strap. 4. Disengage the GLM’s locking tabs that protrude through the guide holes on the controller. 5. Use your index finger and thumb to operate the release lever on the exposed end of the GLM. Press the lower end of the release lever with your index finger while pulling the raised end of the release lever up with your thumb. 6. Remove the GLM.
5–34 HSG80 User’s Guide Replacing a PVA Module Use the following instructions in this section to replace a PVA module in either (1) the master enclosure or (2) the first expansion or second expansion enclosure. Note This procedure is not applicable for the M1 shelf. The HSG80 controller can support up to three enclosures: the master enclosure, the first expansion enclosure, and the second expansion enclosure.
Replacement Procedures 5–35 6. Enter option 3, Replace a PVA module from the FRUTIL Main menu. FRUTIL displays the PVA Replacement menu: FRUTIL PVA Replacement Menu: 1. Master Enclosure (ID 0) 2. First Expansion Enclosure (ID 2) 3. Second Expansion Enclosure (ID 3) 4. Exit Enter Choice: 1, 2, 3, or 4 -> Note The HSG80 controller can support up to three enclosures. The FRUTIL PVA Replacement Menu has options for three enclosures regardless of how many enclosures are connected. 7.
5–36 HSG80 User’s Guide In a dual-redundant configuration, FRUTIL also displays: The configuration has two controllers. To restart the other controller: 1. Type ’restart other_controller’. 2. Press and hold the reset button while inserting the program card on the slot A [or B] controller, then release the reset button. The controller will restart. Field Replacement Utility terminated. 13. To allow the “other controller” to restart, type the following command: RESTART OTHER _CONTROLLER 14.
Replacement Procedures 5–37 4. Start FRUTIL with the following command: RUN FRUTIL FRUTIL displays the following: Do you intend to replace this controller’s cache battery? Y/N 5. Enter N(o). FRUTIL displays the FRUTIL Main menu: FRUTIL Main Menu: 1. Replace or remove a controller or cache module 2. Install a controller or cache module 3. Replace a PVA module 4. Replace an I/O module 5. Exit Enter choice: 1, 2, 3, 4, or 5 -> 6. Enter option 3, Replace a PVA module from the FRUTIL Main menu.
5–38 HSG80 User’s Guide 10. Press return and wait for FRUTIL to quiesce the device ports. This may take several minutes. FRUTIL displays the following: All device ports quiesced. Using the power switch, power down expansion cabinet #2 [or #3] and replace the PVA. 11. Power down the appropriate expansion cabinet. 12. Remove the old PVA and install the new PVA. 13. Power on the appropriate expansion cabinet. FRUTIL displays the following: Press return to resume device port activity. 14.
Replacement Procedures 5–39 Replacing an I/O Module Figure 5–6 shows a rear view of the BA370 enclosure and the location of the six I/O modules (also referred to as ports). Use the following steps to replace an I/O module: Note This procedure is not applicable for the M1 shelf. An I/O module can be replaced in either a single-controller or a dualredundant controller configuration using this procedure.
5–40 HSG80 User’s Guide 5. Enter N(o). FRUTIL displays the FRUTIL Main menu: FRUTIL Main Menu: 1. Replace or remove a controller or cache module 2. Install a controller or cache module 3. Replace a PVA module 4. Replace an I/O module 5. Exit Enter choice: 1, 2, 3, 4, or 5 -> Note The HSG80 controller can support up to three enclosures.
Replacement Procedures 5–41 11. Install a new I/O module. 12. Connect the cables (there may be one or two) to the I/O module. 13. Press return to resume device port activity. When all port activity has restarted, FRUTIL displays the following: I/O module replacement complete. In a dual-redundant configuration, FRUTIL also displays: The configuration has two controllers. To restart the other controller: 1. Type ’restart other_controller’. 2.
5–42 HSG80 User’s Guide Replacing DIMMs Use the following steps in “Removing DIMMs” and “Installing DIMMs” to replace DIMMs in a cache module. The cache module may be configured as shown in Figure 5–7 and Table 5–1.
Replacement Procedures 5–43 Caution ESD can easily damage a cache module or a DIMM. Wear a snug-fitting, grounded ESD wrist strap. Removing DIMMs Use the following steps to remove a DIMM from a cache module: 1. Remove the cache module using the steps in either “Removing the Cache Module in a Single Controller Configuration,” page 5–6, or “Removing a Cache Module in a Dual-Redundant Controller Configuration,” page 5–21. 2.
5–44 HSG80 User’s Guide Installing DIMMs Use the following steps to install a DIMM in a cache module: 1. Insert the DIMM straight into the socket and ensure that the notches in the DIMM align with the tabs in the socket (see Figure 5–8). Figure 5–8 Installing a DIMM Retaining clip (2x) CXO6163A 2. Press the DIMM gently until it’s seated in the socket. 3. Double-check to ensure both ends of the DIMM are firmly seated in the slot and both retaining clips engage the DIMM. 4.
Replacement Procedures 5–45 Replacing a Fibre Cable or Hub Use the following steps in “Remove a Fibre Cable or Hub” and “Install a Fibre Cable or Hub” to replace a cable connected to either side of your hub or to replace the hub itself. Remove a Fibre Cable or Hub Use the following steps to remove a cable connected to either side of your hub or to remove the hub itself: 1. Shut down the host system. 2. Shut down the controllers. In single-controller configurations, shut down “this controller.
5–46 HSG80 User’s Guide Replacing a PCMCIA Card Use the following steps to replace a PCMCIA (program) card: Caution The new PCMCIA card must have the same software version as the PCMCIA card being replaced. See “Installing a New Program Card,” page 6–2, for more information. 1. From a host console, stop all host activity and dismount the logical units in the subsystem. 2. Connect a maintenance PC or terminal to one of the controllers’ maintenance port in your subsystem. 3. Shut down the controllers.
Replacement Procedures 5–47 Replacing a Failed Storageset Member If a disk drive fails in a RAIDset or mirrorset, the controller automatically places it into the failedset. If the spareset contains a replacement drive that satisfies the storageset’s replacement policy, the controller automatically replaces the failed member with the replacement drive.
5–48 HSG80 User’s Guide Shutting Down the Subsystem Use the following steps to shut down a subsystem: 1. From a host console, stop all host activity and dismount the logical units in the subsystem. 2. Connect a maintenance PC or terminal to the maintenance port of one of the controllers in your subsystem. 3. Shut down the controllers. In single controller configurations, you only need to shut down “this controller.
Replacement Procedures 5–49 Figure 5–9 Battery Disable Switch ECB 1 ECB 2 Power connector Status LED Battery disable switch CXO6164A 2. The batteries are no longer powering the cache module. Note To return to normal operation, apply power to the storage subsystem. The cache battery will be enabled when the subsystem is powered on.
5–50 HSG80 User’s Guide Restarting the Subsystem Use the following steps to restart a subsystem: 1. Plug in the subsystem’s power cord, if it is not already plugged in. 2. Turn on the subsystem. The controllers automatically restart and the ECBs automatically re-enable themselves to provide backup power to the cache modules.
6–1 CHAPTER 6 Upgrading the Subsystem This chapter provides instructions for upgrading the controller software, installing software patches, upgrading firmware on a device, upgrading from a singlecontroller configuration to a dual-redundant controller configuration, and upgrading cache memory. Electrostatic Discharge Electrostatic discharge (ESD) is a common problem and may cause data loss, system down time, and other problems.
6–2 HSG80 User’s Guide Upgrading Controller Software You can upgrade the controller’s software two ways: n n Install a new program card that contains the new software. Download a new software image, and use the menu-driven Code Load/Code Patch (CLCP) utility to write it onto the existing program card. You may also use this utility to install, delete, and list patches to the controller software.
Upgrading the Subsystem 6–3 6. Press and hold the reset button while inserting the new program card; “this controller” automatically restarts. The controller is ready to ahndle I/O when the CLI is responsive. 7. Replace the ESD program card cover on “this controller.” 8. In a dual-redundant controller configuration, repeat steps 4 through 7 for teh “other controller.” 9. Mount the storage units on the host.
6–4 HSG80 User’s Guide Figure 6–1 Location of Write-Protection Switch Write protected Write CXO5873A 6. Start CLCP with the following command: RUN CLCP CLCP displays the following: Select an option from the following list: Code Load & Patch local program Main Menu 0: 1: 2: 3: Exit Enter Code LOAD local program Enter Code PATCH local program Enter EMU Code LOAD Utility Enter option number (0..3) [0] ? 7.
Upgrading the Subsystem 6–5 8. Enter option 1, Use the SCSI Host Port, from the menu. CLCP displays the following: WARNING: proceeding with Controller Code Load will overwrite the current Controller code image with a new image. Do you want to continue (y/n) [n]: ? 9. Enter Y(es) and the download starts. When the download is complete, CLCP writes the new image to the program card and restarts the controller. This process takes one to three minutes. Go to step 15. 10.
6–6 HSG80 User’s Guide Using CLCP to Install, Delete, and List Software Patches Use CLCP to manage software patches. These small programming changes are placed into the controller’s non-volatile memory and become active as soon you restart the controller. There is space for about ten patches, depending upon the size of the patches you’re installing. Keep the following points in mind while installing or deleting patches: n n n n Patches are associated with specific software versions.
Upgrading the Subsystem 6–7 5. Enter option 2, Enter Code PATCH local program. CLCP displays the following: You have selected the Code Patch local program. is used to manage software code patches. This program Select an option from the following list: Type ^Y or ^C (then RETURN) at any time to abort Code Patch. Code Patch Main Menu 0: Exit 1: Enter a Patch 2: Delete Patches 3: List Patches Enter option number (0..3) [0] ? 6. Enter option 1, Enter a Patch, to install a patch.
6–8 HSG80 User’s Guide 3. Start CLCP with the following command: RUN CLCP CLCP displays the following: Select an option from the following list: Code Load & Patch local program Main Menu 0: Exit 1: Enter Code LOAD local program 2: Enter Code PATCH local program 3: Enter EMU Code LOAD utility Enter option number (0..3) [0] ? 4. Enter option 2, Enter Code PATCH local program. CLCP displays the following: You have selected the Code Patch local program. is used to manage software code patches.
Upgrading the Subsystem 6–9 6. Enter the software version of the patch to delete and press return. CLCP displays the following: Patch Number to delete ? 7. Enter the patch number to delete and press return. CLCP displays the following: The following patches have been selected for deletion: Software Version - Patch # xxxx xxxx Do you wish to continue (y/n) [n] ? 8. Enter Y(es) and the patches are deleted.
6–10 HSG80 User’s Guide 3. Enter option 2, Enter Code PATCH local program. CLCP displays the following: You have selected the Code Patch local program. is used to manage software code patches. This program Select an option from the following list: Type ^Y or ^C (then RETURN) at any time to abort Code Patch. Code Patch Main Menu 0: Exit 1: Enter a Patch 2: Delete Patches 3: List Patches Enter option number (0..3) [0] ? 4. Enter option 3, List Patches, to list patches.
Upgrading the Subsystem 6–11 Upgrading Firmware on a Device Use HSUTIL to upgrade a device with firmware located in contiguous blocks at a specific LBN on a source disk drive configured as a unit on the same controller. Upgrading firmware on a disk is a two-step process as shown in Figure 6–2: first, copy the new firmware from your host to a disk drive configured as a unit in your subsystem, then use HSUTIL to load the firmware onto the devices in the subsystem.
6–12 HSG80 User’s Guide n n n n HSUTIL cannot install firmware on devices that have been configured as single disk drive units or as members of a storageset, spareset, or failedset. If you want to install firmware on a device that has previously been configured as a single disk drive, delete the unit number and storageset name associated with it. During the installation, the source disk drive is not available for other subsystem operations.
Upgrading the Subsystem 6–13 4. Start HSUTIL with the following command: RUN HSUTIL HSUTIL displays the following: HSUTIL Main Menu: 0. Exit 1. Disk Format 2. Disk Device Code Load 3. Tape Device Code Load 4. Disaster Tolerance Backend Controller Code Load Enter function number: (0:4) [0]? 5. Enter option 2, Disk Device Code Load, from the HSUTIL menu. 6. Choose the single-disk unit as the source disk for the download. 7. Enter the starting LBN of the firmware image—usually LBN 0. 8.
6–14 HSG80 User’s Guide HSUTIL Messages While you are formatting disk drives or installing new firmware, HSUTIL may produce one or more of the messages in Table 6-1 (many of the self-explanatory messages have been omitted). Table 6–1 HSUTIL Messages and Inquiries Message Description Insufficient resources HSUTIL cannot find or perform the operation because internal controller resources are not available.
Upgrading the Subsystem 6–15 Table 6–1 HSUTIL Messages and Inquiries (Continued) Message Description Does the target device support only the HSUTIL detects that an unsupported device has been download microcode and save? selected as the target device. You must specify whether the device supports the SCSI Write Buffer command’s download and save function. Should the code be downloaded with a HSUTIL detects that an unsupported device has been selected single write buffer command? as the target device.
6–16 HSG80 User’s Guide Upgrading to a Dual-Redundant Controller Configuration Use the following steps to upgrade a single-configuration subsystem to a dual-redundant configuration subsystem. To replace failed components, see Chapter 5, “Replacement Procedures,” for more information.
Upgrading the Subsystem 6–17 4. Enter option 2, Install a controller or cache module, from the FRUTIL Main menu. FRUTIL displays the Install Options menu: Install Options: 1. Other controller and cache module 2. Other controller module 3. Other cache module 4. Exit Enter choice: 1, 2, 3, or 4 -> 5. Enter option 1, Other controller and cache module, from the Install Options menu. FRUTIL display the following: Insert the both the slot B controller and cache module? Y/N 6. Enter Y(es) and press return.
6–18 HSG80 User’s Guide 8. Disable the ECB to which you’re connecting the new cache module by pressing the battery disable switch until the status light stops blinking— about five seconds. Caution The ECB must be disabled—the status light is not lit or is not blinking—before connecting the ECB cable to the cache module. Failure to disable the ECB could result in the ECB being damaged. Make sure you align the cache module and controller in the appropriate guide rails.
Upgrading the Subsystem 6–19 Note If the controller you’re installing was previously used in another subsystem, it will need to be purged of the controller’s old configuration (see “CONFIGURATION RESET,” page B–45). 12. Wait for FRUTIL to terminate and connect the hub cables to the new controller. Note One or two hub cables may be attached, depending on the configuration. 13. To allow the “other controller”to restart, type the following command: RESTART OTHER _CONTROLLER 14.
6–20 HSG80 User’s Guide Upgrading Cache Memory The cache module may be configured as shown in Figure 5–7 on page 5-42 and Table 6–2 on page 6–20. Table 6–2 Cache Module Memory Configurations Memory DIMMs Quantity Location 64 MB 32 MB 2 MC0-1 and MC1-3 128 MB 32 MB 4 MC0-1, MC0-2, MC1-3, and MC1-4 256 MB 128 MB 2 MC0-1 and MC1-3 512 MB 128 MB 4 MC0-1, MC0-2, MC1-3, and MC1-4 In order to upgrade cache memory, the controller must be shut down.
Upgrading the Subsystem 6–21 Caution The ECB must be disabled—the status light is not lit or is not blinking—before disconnecting the ECB cable from the cache module. Failure to disable the ECB could result in cache module damage. 5. Disconnect the ECB cable from the cache module. 6. Disengage the two retaining levers, remove the cache module, and place the cache module onto a grounded antistatic mat.
6–22 HSG80 User’s Guide 16. Set the subsystem date and time. In single controller configurations, set “this controller.” In dual-redundant controller configurations, set “this controller,” then set the “other controller” with the following command: SET THIS_CONTROLLER TIME= dd-mmm-yyyy:hh:mm:ss SET OTHER_CONTROLLER TIME= dd-mmm-yyyy:hh:mm:ss 17. Disconnect the PC or terminal from the controller’s maintenance port.
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.
A–2 HSG80 User’s Guide Device Profile Type ___ Platter disk drive ___ Tape Drive ___ Optical disk drive ___ CD-ROM Device Name ______________________________________________________________ Unit Number______________________________________________________________ Device Switches Transportability ___ No (default) ___ Yes Initialize Switches Chunk size Save Configuration Metadata ___ Automatic (default) ___ 64 blocks ___ 128 blocks ___ 256 blocks ___ Other: ___ No (default) ___ Yes ___ Destroy (de
System Profiles A–3 Storageset Profile Type ___ RAIDset ___ Mirrorset ___ Stripeset ___ Striped Mirrorset Storageset Name ___________________________________________________________ Disk Drives ________________________________________________________________ Unit Number ______________________________________________________________ Partitions Unit # Unit # Unit # Unit # Unit # Unit # Unit # Unit # % % % % % % % % RAIDset Switches Reconstruction Policy Reduced Membership Replacement Po
A–4 HSG80 User’s Guide Enclosure Template Power Supply Power Supply Power Supply Power Supply Power Supply Power Supply Power Supply Power Supply
B–1 APPENDIX B 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.
B–2 HSG80 User’s Guide 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.
CLI Commands n n n n n B–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.
B–4 HSG80 User’s Guide Specific keys or a combination of keys allow you to recall and edit the last four commands. This feature can save time and help prevent mistakes when you need to enter similar commands during the configuration process. Table B–1 lists the keys used to recall and edit commands.
CLI Commands B–5 Command Syntax Commands to the controller must use the following command structure: COMMAND parameter SWITCHES n n n Command. A word or phrase expressed as a verb that is used to instruct the controller what to do. Every CLI command begins with a command. Commands are represented in this manual in capitalized form. Parameter. When required in the command, one or more words or phrases that supply necessary information to support the action of the command.
CLI Commands B–7 ADD CONNECTIONS Adds the specified host connection to the table of known connections. This table is maintained in NVRAM. The maximum table length is 32 connections; if the table contains 32 entries, new connections cannot be added unless some old ones are deleted. There are two mechanisms for adding a new connection to the table, as follows: n Physically connecting a host adapter to a controller port.
B–8 HSG80 User’s Guide form of a default connection name. The form of a default connection name is !NEWCONnn. Note The default connection name is assigned automatically by the controller when the connection is physically made between a host adapter and a controller port. Default connection names are assigned only by the controller. HOST_ID=nnnn-nnnn-nnnn-nnnn Host_ID is the worldwide name of the host. It is a 16-character hexadecimal number.
CLI Commands B–9 In transparent failover mode and normal mode, host connections on controller port 1 have an offset of 0 and host connections on controller port 2 have an offset of 100. These are the default offset values. The relationship between LUN number, unit number, and offset is as follows: n n n LUN number = unit number - offset. Logical unit number or LUN number = the logical unit number presented to the host connection. Unit number = the number assigned to the unit in the ADD UNIT command.
B–10 HSG80 User’s Guide See also ADD UNIT DELETE connections SET connection-name
CLI Commands B–11 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.
B–12 HSG80 User’s Guide 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) that is used to improve data reliability, error detection, and the ability to recover data.
CLI Commands B–13 Examples To add DISK10000 at port 1, target 0, LUN 0, type: ADD DISK DISK10000 1 0 0 To add DISK40200 as a transportable disk drive to port 4, target 2, LUN 0, use: ADD DISK DISK40200 4 2 0 TRANSPORTABLE To add a disk drive named DISK30200 as non-transportable disk to port 3, target 2, LUN 0, and to set the data transfer rate to 10 MHz, enter the following command on one line.
CLI Commands B–15 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 (.
B–16 HSG80 User’s Guide 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. POLICY=BEST_FIT POLICY=BEST_PERFORMANCE (Default) NOPOLICY Sets the selection criteria the controller uses to choose a replacement disk from the spareset when a mirrorset member fails.
CLI Commands B–17 Specify READ_SOURCE=LEAST_BUSY to direct read requests to the mirrorset disk with the least amount of work in its queue. If multiple members have equally short queues, the controller queries normal disks for each read request as it would when READ_SOURCE= ROUND_ROBIN is specified. Specify READ_SOURCE=ROUND_ROBIN to sequentially direct read requests to each mirrorset disk. The controller equally queries all normal disks for each read request.
CLI Commands B–19 ADD RAIDSET Names a RAIDset and adds the RAIDset to the controller’s configuration. DIGITAL 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 containername parameter in the command. The data capacity of the RAIDset is determined by the storage size of the smallest member.
B–20 HSG80 User’s Guide 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. If more than one disk drive in the spareset is the correct size, the controller selects a disk drive giving the best performance.
CLI Commands B–21 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. Verify the RAIDset contains all but one of its disks before specifying the REDUCED switch.
B–22 HSG80 User’s Guide Caution Data contained on the RAIDset will be erased if you reinitialize the RAIDset.
CLI Commands B–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.
CLI Commands B–25 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 containername parameters specified. Syntax ADD STRIPESET stripeset-name container-name1 container-name2 [container-nameN] Parameters stripeset-name Assigns a name to the stripeset.
B–26 HSG80 User’s Guide Examples To create a stripeset named STRIPE1 with three disks: DISK10000, DISK20100, and DISK30200, enter: ADD ADD ADD ADD DISK DISK10000 1 0 0 DISK DISK20100 2 1 0 DISK DISK30200 3 2 0 STRIPESET STRIPE1 DISK10000 DISK20100 DISK30200 To create a stripeset named STRIPE1 and then create a logical unit from it, type: 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 to create
CLI Commands B–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 logical unit.
HSG80 User’s Guide container-name Specifies the name of the container (disk drive, device, storageset, or partition) that is used to create the unit. A maximum of 48 devices can make up one unit. Switches Table B–2 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.
CLI Commands B–29 bus, you can use this switch to restrict hosts from accessing certain units. This switch limits visibility of specific units from certain hosts. For example, if two hosts are on the same bus, you can restrict each host to access only specific units. If you enable another host ID(s), previously enabled host(s) are not disabled. The new ID(s) are added. If you wish to enable only certain ID(s), disable all access paths (DISABLE_ACCESS_PATH=ALL), then enable the desired ID(s).
B–30 HSG80 User’s Guide The MAXIMUM_CACHED_TRANSFER switch affects both read and write-back cache when set on a controller that has read and write-back caching. PREFERRED_PATH=OTHER_CONTROLLER PREFERRED_PATH=THIS_CONTROLLER NOPREFERRED_PATH (Default) May be set only when dual-redundant controllers are operating in a multiple bus failover configuration. In a multiple bus failover configuration, the host determines which controller the units are accessed through.
CLI Commands B–31 READ_CACHE (Default) NOREAD_CACHE Sets the controller’s cache read policy function. Read caching improves performance in almost all situations. Therefore, it is recommended you leave its default setting, READ_CACHE enabled. However, under certain conditions, such as when performing a backup, read caching may not be necessary since only a small amount of data is cached.
B–32 HSG80 User’s Guide WRITE_PROTECT (Default) NOWRITE_PROTECT Tells the controller whether data contained on the unit can be overwritten. Specify WRITE_PROTECT to prevent the host from writing data to the unit. However, the controller may still write to a write-protected RAIDset to complete a reconstruct operation and metadata, reconstruct data, and copy data may still be written to RAIDsets and mirrorsets. Specify NOWRITE_PROTECT to allow the host to write data to the unit.
CLI Commands B–33 Examples This example shows how to create unit D102 from a single-disk drive named DISK10000 and sets the host’s access to the unit through “this controller.” ADD DISK DISK10000 1 0 0 INITIALIZE DISK10000 ADD UNIT D102 DISK10000 PREFERRED_PATH=THIS_CONTROLLER This example shows how to create unit D107 from a RAIDset named RAID9 and instructs the unit to take advantage of the controller’s writeback caching feature.
CLI Commands B–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.
CLI Commands B–37 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: n n When the controller or cache modules have been replaced, resulting in mismatched data between the controllers.
B–38 HSG80 User’s Guide Specify NODESTROY_UNFLUSHED_DATA in the following situations: n n 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: n n 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.
CLI Commands B–39 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.
CLI Commands B–41 CLEAR_ERRORS unit-number LOST_DATA Clears lost data errors on a unit; 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.
B–42 HSG80 User’s Guide See also CLEAR_ERRORS CLI CLEAR_ERRORS INVALID_CACHE CLEAR_ERRORS UNKNOWN CLEAR_ERRORS UNWRITEABLE_DATA
CLI Commands B–43 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.
CLI Commands B–45 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 B–71. Specify the CONFIGURATION RESET command on “this controller” in nofailover mode only.
CLI Commands B–47 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.
B–48 HSG80 User’s Guide See also CONFIGURATION RESET CONFIGURATION SAVE INITIALIZE
CLI Commands B–49 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 dual-redundant configuration, issue this command to both controllers.
CLI Commands B–51 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.
B–52 HSG80 User’s Guide smaller than the size specified because metadata also occupies some of the partition’s allocated space. Specify LARGEST in the following situations: n n To have the controller create the largest partition possible from unused space on the disk or storageset. To create the last partition on a container. Because the remaining space is not equal to an exact percentage value, specifying LARGEST allows you to optimize use of the remaining space.
CLI Commands B–53 Example This example shows how to create a RAIDset named RAID9 and divide it into four equal parts. It also creates host-addressable units for each partition.
CLI Commands B–55 DELETE connections Deletes a host connection entry from the table of known connections. This command deletes a specified connection from the table of known connections maintained by the controller. The table of known host connections is maintained in the controllers NVRAM. Once a connection is added to the table, it stays there, even if the physical connection between host adapter and controller port is severed.
B–56 HSG80 User’s Guide Examples Deletes the host connection Server1 from the table of known connections (unless the access path to Server1 is specifically enabled for one or more unit.
CLI Commands B–57 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 RAIDset, or a RAIDset belonging to a unit; you must first delete the higher-level container or containers. Note This command does not delete sparesets or failedsets. You cannot delete spareset and failedset containers. See the DELETE FAILEDSET and DELETE SPARESET commands for details.
B–58 HSG80 User’s Guide See also DELETE FAILEDSET DELETE SPARESET UNMIRROR
CLI Commands B–59 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 disks from the storage shelf for testing, repair, or replacement. You should consider all disk drives in the failedset defective. Repair or replace disks found in the failedset.
CLI Commands B–61 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.
CLI Commands B–63 DELETE unit-number Deletes a logical unit from the controller configuration. The host cannot address deleted units. If the unit’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.
CLI Commands B–65 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.
B–66 HSG80 User’s Guide See also ADD DISK ADD STORAGESET ADD STRIPESET CREATE_PARTITION DELETE unit-number SHOW
CLI Commands B–67 DIRECTORY Lists the diagnostics and utilities available on “this controller.” Syntax DIRECTORY Example The example below shows how to display a directory listing: DIRECTORY HSUTIL V82G D CHVSN V82G D CLCP V82G D CLONE V82G D CONFIG V82G D DILX V82G D DIRECT V82G D DSTAT V82G D FRUTIL V82G D FMU V82G D VTDPY V82G D Note CHVSN and DSTAT are not user utilities. They should be used by DIGITAL authorized service personnel only.
CLI Commands B–69 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 To display information regarding the HELP command, type: HELP Help may be requested by typing a question mark (?) at the CLI prompt.
CLI Commands B–71 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.
B–72 HSG80 User’s Guide 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. Note These are used to set the SCSI parameters reported to the host. They should not be used unless there is a compatibility problem with the existing defaults.
CLI Commands B–73 See “Chunk Size,” page 3–47 for information regarding recommended chunk size settings for your application. DESTROY (Default) NODESTROY Controls how the metadata on the initialized container is to be handled. Note The DESTROY and NODESTROY switches are only valid with mirrorsets and striped mirrorsets. Specify NODESTROY to preserve forced error metadata during the initialization process. Use the NODESTROY switch only when a unit is to be created from disk drives REDUCED from mirrorsets.
B–74 HSG80 User’s Guide Specify NOSAVE_CONFIGURATION if you do not want to store a copy of the controller configuration on a container. See “Backing Up Your Subsystem Configuration,” page 3–23, for more information regarding SAVE_CONFIGURATION.
CLI Commands B–75 This example shows how to initialize RAIDset RAID9 with a chunk size of 20: ADD DISK DISK10200 1 2 0 ADD DISK DISK20200 2 2 0 ADD DISK DISK30200 3 2 0 ADD RAIDSET RAID9 DISK10200 DISK20200 DISK30200 INITIALIZE RAID9 CHUNKSIZE=20 This example shows how to initialize DISK40400 and preserve the data after it is removed (reduced) from a mirrorset: REDUCE DISK40400 INITIALIZE DISK40400 NODESTROY
CLI Commands B–77 LOCATE Indicates the physical location of configured units, storagesets, and devices by flashing the green 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.
B–78 HSG80 User’s Guide Not all devices have a device fault LED. Therefore, they do not appear to respond to the LOCATE command. UNITS Causes the green device fault LEDs of all devices used by the units to flash. This command is useful to determine which devices are not currently configured into logical units. Enter LOCATE CANCEL to turn off the device fault LEDs. container-name Causes the green device fault LEDs on the devices within the container-name to flash.
CLI Commands B–79 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, then enter the ADD MIRRORSET command to create a mirrorset from disk drives not already members of higher level containers.
B–80 HSG80 User’s Guide data, and copying takes less time. However, overall controller performance is reduced during copying. 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.
CLI Commands B–81 Example This example shows how to create a one-member mirrorset from each member of a stripeset. These commands set the nominal number of members in each mirrorset to two and add a second disk to each mirrorset. It is not necessary to initialize the mirrorsets or add them as units; the higher-level structure of the stripeset is carried down to the mirrorsets.
CLI Commands B–83 POWEROFF Powers off all disk units in a cabinet and turns off the cabinet power. 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 charger on after the POWEROFF command is issued. Specify BATTERY_OFF to turn off the ECB charger after the POWEROFF command is issued.
B–84 HSG80 User’s Guide Table B–3 shows what action will be taken depending on the switch settings and the results of the attempted flush: Table B–3 POWEROFF Switch Settings Battery Switch Override Switch Flush Results BATTERY_ON OVERRIDE_BAD_FLUSH Success BATTERY_ON OVERRIDE_BAD_FLUSH Failure BATTERY_ON NO_OVERRIDE_BAD_FLUSH Success BATTERY_ON NO_OVERRIDE_BAD_FLUSH Failure BATTERY_OFF OVERRIDE_BAD_FLUSH Success BATTERY_OFF OVERRIDE_BAD_FLUSH Failure BATTERY_OFF NO_OVERRIDE_BAD_FLUSH Suc
CLI Commands B–85 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.
B–86 HSG80 User’s Guide Only normal members can be reduced. A normal member is a mirrorset member whose entire contents are the same as all other normal members within the mirrorset. Note An error is displayed if you attempt to reduce a mirrorset so that there would not be any normal member remaining. Syntax REDUCE disk-name1 disk-name2 disk-name3... Parameters disk-name1 disk-name2 disk-name3... Specifies the names of the disk or disks to be removed from the mirrorset or mirrorsets.
CLI Commands REDUCE DISK20100 DISK20500 DISK40200 SHOW MIRRORSETS Name Storageset Uses Used by -----------------------------------------------------------------------MIRR1 mirrorset DISK10100 STRIPE1 MIRR2 MIRR3 mirrorset mirrorset See also ADD MIRRORSET MIRROR RUN CLONE SHOW MIRRORSET SET mirrorset-name DISK10200 DISK30300 STRIPE1 STRIPE1 B–87
CLI Commands B–89 RENAME Renames a specified container or a specified host connection. Syntax RENAME old-name new-name Parameters old-name Specifies the existing name of the container or host connection. new-name Assigns the new name for the container or the host connection. See “Command Syntax,” page B–5, for information regarding container naming rules.
CLI Commands B–91 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.
B–92 HSG80 User’s Guide 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 WriteBack Caching,” page 1–21 for considerations when implementing write-back cache. Do not perform any hardware changes until the controller flushes the cache. Specify IMMEDIATE_SHUTDOWN to instruct the controller to restart immediately without flushing data from the write-back cache to devices.
CLI Commands B–93 RETRY_ERRORS UNWRITEABLE_DATA Causes the controller to attempt to write previously unwriteable data from the write-back 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.
CLI Commands B–95 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: n n n n n CHVSN—This is not a user utility. This utility may be used by DIGITAL authorized service personnel only.
B–96 HSG80 User’s Guide The autoconfigure mode is the most thorough mode and allows you to: n n 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: n n n n n n n n n n Test disks you select Perform tests in read-only mode or write-only mode Provide run time and performance summary options Can be run in read-only mode DIRECT—A command used to display a list of all executable dia
CLI Commands Example This example shows how to start the DILX diagnostic program: RUN DILX . . .
CLI Commands B–99 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.
B–100 HSG80 User’s Guide 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 WriteBack Caching,” page 1–21 for considerations when implementing write-back cache. Do not perform any hardware changes until the controller flushes the cache.
CLI Commands B–101 SET connection-name Changes the operating characteristics of a host connection. The SET connection-name command changes the operating parameters of the specified host connection. A host connection is a specific instance of one host connected to one port of one controller through one host adapter Syntax SET connection-name Parameters connection-name This is the name of the host connection.
B–102 HSG80 User’s Guide n Unit number = the number assigned to the unit in the ADD UNIT command. This is the number by which the unit is known internally to the controllers. OPERATING_SYSTEM=OS_name Specifies the operating system of the host.
CLI Commands B–103 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 B–4 lists the switches available with this command. Descriptions of the switches follow the table.
B–104 HSG80 User’s Guide Table B–4 SET controller Switches Switch ALLOCATION_CLASS CACHE_FLUSH_TIMER CACHE_UPS NOCACHE_UPS COMMAND_CONSOLE_LUN NOCOMMAND_CONSOLE_LU N IDENTIFIER NOIDENTIFIER MIRRORED_CACHE NOMIRRORED_CACHE NODE_ID PORT_1_ALPA PORT_2_ALPA PORT_1_TOPOLOGY PORT_2_TOPOLOGY PROMPT SCSI_VERSION TERMINAL_PARITY NOTERMINAL_PARITY TERMINAL_SPEED TIME Values decimal number 1–65535 sec, 10 (default) None None decimal number None assigned during manufacturing 0-EF (hexadecimal value) LOOP_HARD LOOP_S
CLI Commands B–105 ALLOCATION_CLASS Allocation class is a unique identification number assigned to the controller pair under certain operating systems. In Digital open VMS, this is a 2-byte number; 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. It allows the user to place a unique number in the allocation class value (n).
B–106 HSG80 User’s Guide 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. COMMAND_CONSOLE_LUN NOCOMMAND_CONSOLE_LUN (Default) Enable or disables the virtual LUN used with the StorageWorks Command Console. When changed, the new setting for this switch takes effect immediately.
CLI Commands B–107 Issue this switch through only one controller. The controller must contain a valid cache configuration before specifying this switch. See Chapter 2 for rules regarding valid cache configurations. The controllers automatically restart when this switch is specified. Note All unwritten write-cached data is automatically flushed from cache before restart when the MIRRORED_CACHE switch is specified.
B–108 HSG80 User’s Guide PORT_1_TOPOLOGY=LOOP_HARD PORT_1_TOPOLOGY=LOOP_SOFT PORT_1_TOPOLOGY=OFFLINE PORT_2_TOPOLOGY=LOOP_HARD PORT_2_TOPOLOGY=LOOP_SOFT PORT_2_TOPOLOGY=OFFLINE Indicates whether the user or controller selects the ALPA for a host port, or whether the port is to be set offline. LOOP_HARD allows you to pick the ALPA. LOOP_SOFT requests the controller to pick the ALPA. OFFLINE sets the host port offline. Specify OFFLINE for a port when it will not be used.
CLI Commands B–109 TERMINAL_SPEED=baud_rate TERMINAL_SPEED=9600 (Default) Sets the terminal transmission and reception speed (baud rate) to 4800, 9600 (default), or 19200 baud. When changed, the new value entered for this switch takes effect immediately. TIME=dd–mmm–yyyy:hh:mm:ss Sets the date and time. The time is set on both controllers in a dualredundant configuration.When changed, the new value entered for this switch takes effect immediately.
CLI Commands B–111 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.
B–112 HSG80 User’s Guide If you specify the NOTRANSPORTABLE switch and there is no metadata on the unit, the unit must be initialized. If you specify TRANSPORTABLE for a disk that was originally initialized as a NOTRANSPORTABLE, you should initialize the disk. Note DIGITAL recommends you avoid specifying TRANSPORTABLE unless transportability of the device or media is imperative and there is no other way to accomplish moving the data.
CLI Commands B–113 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.
B–114 HSG80 User’s Guide Table B–5 lists the valid EMU set-point temperatures in both Fahrenheit and Celsius.
CLI Commands B–115 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.
CLI Commands B–117 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. Specify NOAUTOSPARE to instruct the controller to leave devices physically replaced in the failedset.
B–118 HSG80 User’s Guide 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. DELETE DISK10000 5. Move DISK10000 to the failedset’s vacant slot.
CLI Commands B–119 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.
B–120 HSG80 User’s Guide 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
CLI Commands B–121 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.
B–122 HSG80 User’s Guide Note No other switches can be set when you specify the MEMBERSHIP switch. If you increase the number of members and specify a replacement policy with the POLICY= switch, the controller automatically adds disk drives from the spareset to the mirrorset until the new number of members is reached, or there are no more suitable disk drives in the spareset.
CLI Commands B–123 Note Normalizing members exist only when you first create a mirrorset or when you clear lost data on a mirrored unit. The controller recognizes the member as normal, and all other original mirrorset members as “normalizing.” New data that is written to the mirrorset is written to all members. The controller copies the data existing before the mirrorset was created on the normal member to the normalizing members.
B–124 HSG80 User’s Guide 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 the disk drive that equals or exceeds the base member size of the mirrorset. Specify NOPOLICY to prevent the controller from automatically replacing a failed disk device.
CLI Commands This example shows how to add disk DISK30200 to the mirrorset MIRR1: SET MIRR1 REPLACE=DISK30200 A copy operation begins immediately on DISK30200.
CLI Commands B–127 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.
B–128 HSG80 User’s Guide Due to the amount of information being passed from one controller to the other, this command may take up to one minute to complete.
CLI Commands B–129 SET NOFAILOVER Reconfigures both controllers to operate in a non-dual-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.
B–130 HSG80 User’s Guide 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.
CLI Commands B–131 SET NOMULTIBUS_FAILOVER Reconfigures both controllers to operate in a non-dual-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.
B–132 HSG80 User’s Guide 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.
CLI Commands B–133 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 hostaddressable unit. Switches POLICY=BEST_FIT POLICY=BEST_PERFORMANCE (Default) NOPOLICY Specifies the replacement policy to use when a member within the RAIDset fails.
B–134 HSG80 User’s Guide 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.
CLI Commands B–135 REPLACE=disk-name Instructs the controller to add a disk member to an existing RAIDset if the following conditions are met: n n 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).
CLI Commands B–137 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 B–6 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.
HSG80 User’s Guide Table B–6 SET unit-number Switches for Existing Containers Container Type Switch ENABLE_ACCESS_PATH DISABLE_ACCESS_PATH MAXIMUM_CACHED_ TRANSFER IDENTIFIER NOIDENTIFIER PREFERRED_PATH NOPREFERRED_PATH READ_CACHE NOREAD_CACHE READAHEAD_CACHE NOREADAHEAD_CACHE WRITE_PROTECT NOWRITE_PROTECT WRITEBACK_CACHE NOWRITEBACK_CACHE RUN NORUN B–138 RAIDset ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Stripeset ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Mirrorset ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ NoTransportable Disk ✔ ✔ ✔ ✔ ✔
CLI Commands B–139 Warning 1000: Access IDs in addition to the one(s) specified are still enabled. If you wish to enable ONLY the id(s) listed, disable all access paths (DISABLE_ACCESS_PATH=ALL), then enable the ones previously listed. MAXIMUM_CACHED_TRANSFER=n MAXIMUM_CACHED_TRANSFER=32 (Default) Sets the largest number of write blocks to be cached by the controller. The controller does not cache any transfers over the set size. Accepted values are 1 through 1024.
B–140 HSG80 User’s Guide 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. READ_CACHE (Default) NOREAD_CACHE Switches enable or disable the read-cache function for the unit. Read caching improves performance in almost all situations, so it is generally recommended to leave it enabled.
CLI Commands B–141 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 partitioned units. WRITE_PROTECT NOWRITE_PROTECT (Default) Assigns to the unit’s a write-protect policy. 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.
B–142 HSG80 User’s Guide Note The controller may take up to five minutes to flush data contained within the write-back cache when you specify the NOWRITEBACK_CACHE switch.
CLI Commands B–143 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.
B–144 HSG80 User’s Guide device-type Specifies the type of devices you want to be displayed. Valid choices are: n n DEVICES—Shows all devices attached to the controller DISKS—Shows all disks 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. For example, SHOW STRIPE1 displays information about the stripeset named STRIPE1.
CLI Commands B–145 1234 5678 9ABC EF00 0001 0001 3056 00D2 Each single disk unit or storage device in your subsystem is assigned a unique unit ID number. The controller constructs a unit ID number for each device you add to the subsystem. The ID number consists of the controller’s worldwide node ID and a unique, internally generated serial stamp. You cannot set or change unit ID numbers. Unit ID numbers stay with the unit when you move the unit from one slot to another in the enclosure.
B–146 HSG80 User’s Guide This example shows how to display a complete listing of the mirrorset named MIRR1: SHOW MIRR1 Name Storageset Uses Used by -----------------------------------------------------------------------------MIRR1 mirrorset DISK50300 S0 DISK60300 Switches: POLICY (for replacement) = BEST_PERFORMANCE COPY (priority) = NORMAL READ_SOURCE = LEAST_BUSY MEMBERSHIP = 2, 2 members present State: NORMAL DISK60300 (member DISK50300 (member 0) is NORMAL 1) is NORMAL Size: 17769177 blocks Thi
CLI Commands B–147 Extended information: Terminal speed 19200 baud, eight bit, no parity, 1 stop bit Operation control: 00000001 Security state code: 33506 Configuration backup disabled Other controller not responding - RESET signal NOT asserted - NINDY ON Temperature within optimum limit.
CLI Commands B–149 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.
B–150 HSG80 User’s Guide 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. Specify IMMEDIATE_SHUTDOWN to cause the controller to shutdown immediately without checking for online devices or before flushing data from the write-back cache to devices.
CLI Commands B–151 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 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.
C–1 APPENDIX C LED Codes This appendix shows and describes the LED codes that you may encounter while servicing the controller, cache module, and external cache battery.
C–2 HSG80 User’s Guide Operator Control Panel LED Codes Use Table C–1 to interpret solid OCP patterns and Table C–2 to identify flashing OCP patterns. Note that in the ERROR column of Table C-1, there are two separate descriptions. The first denotes the actual error message that appears on your terminal, and the second provides a more detailed explanation of the designated error.
LED Codes C–3 Solid OCP Patterns Table C–1 Solid OCP Patterns Pattern OCP Code ■● ● ● ●● ● 3F Error DAEMON diagnostic failed hard in non-fault tolerant mode Repair Action Verify that cache module is present. If the error persists, replace controller.
C–4 HSG80 User’s Guide Table C–1 Solid OCP Patterns (Continued) Pattern OCP Code ■● ● ● ❍❍❍ 38 Error Controller operation terminated Repair Action Reset controller Last Failure event required termination of controller operation (e.g.
LED Codes Table C–1 C–5 Solid OCP Patterns (Continued) Pattern OCP Code ■● ● ❍❍ ❍❍ 30 Error Repair Action An unexpected bugcheck occurred before subsystem initialization completed Reinsert controller. If that does not correct the problem, reset the controller. If the error persists, try resetting the controller again, and replace it if no change occurs.
C–6 HSG80 User’s Guide Table C–1 Solid OCP Patterns (Continued) Pattern OCP Code ■● ❍ ●❍ ●❍ 2A Error All cabinet IO modules are not of the same type Cabinet I/O modules are a combination of single-sided and differential ■● ❍ ●❍ ❍● 29 EMU protocol version incompatible The microcode in the EMU and the software in the controller are not compatible ■● ❍ ●❍ ❍❍ 28 An unexpected Machine Fault/ NMI occurred during Last Failure processing Repair Action Ensure that the I/O modules in an extended subsys
LED Codes Table C–1 C–7 Solid OCP Patterns (Continued) Pattern OCP Code ■● ❍ ❍● ❍● 25 Error Recursive Bugcheck detected The same bugcheck has occurred three times within ten minutes, and controller operation has terminated. ■❍❍ ❍❍❍❍ 0 No program card detected or kill asserted by other controller Controller unable to read program card ❏❍❍ ❍❍❍❍ 0 Catastrophic controller or power failure Repair Action Reset the controller.
C–8 HSG80 User’s Guide Flashing OCP Patterns Table C–2 Flashing OCP Patterns OCP Code Pattern Error Repair Action ■ ❍❍ ❍❍ ❍● 1 Program card EDC error Replace program card ■ ❍❍ ❍● ❍❍ 4 Timer zero on the processor is bad Replace controller ■ ❍❍ ❍● ❍● 5 Timer one on the processor is bad Replace controller ■ ❍❍ ❍● ● ❍ 6 Processor Guarded Memory Unit (GMU) is bad Replace controller ■ ❍❍ ●❍ ● ● B Nonvolatile Journal Memory (JSRAM) First, verify correct upgrade (see Release Notes).
LED Codes Table C–2 Flashing OCP Patterns (Continued) Pattern OCP Code Error Repair Action ■ ● ●❍ ❍❍ ❍ 30 The JSRAM battery is bad Replace controller ■ ● ●❍ ❍● ❍ 32 First-half diagnostics of the Time of Year Clock failed Replace controller ■ ● ●❍ ❍● ● 33 Second-half diagnostics of the Time of Year Clock failed Replace controller ■ ● ●❍ ●❍ ● 35 The processor bus-to-device bus bridge Replace controller chip is bad ■ ● ●● ❍● ● 3B There is an unnecessary interrupt pending Replace contro
D–1 APPENDIX D Event Reporting: Templates and Codes This appendix describes the event codes that the fault-management software generates for spontaneous events and last-failure events. The HSG80 controller uses various codes to report different types of events, and these codes are presented in template displays.
D–2 HSG80 User’s Guide Passthrough Device Reset Event Sense Data Response Events reported by passthrough devices during host/device operations are conveyed directly to the host system without intervention or interpretation by the HSG80controller, with the exception of device sense data that is truncated to 160 bytes when it exceeds 160 bytes.
Event Reporting: Templates and Codes D–3 Last Failure Event Sense Data Response Unrecoverable conditions detected by either software or hardware and certain operator-initiated conditions result in the termination of HSG80 controller operation. In most cases, following such a termination, the controller will attempt to restart (that is, reboot) with hardware components and software data structures initialized to the states necessary to perform normal operations (see Figure D–2).
D–4 HSG80 User’s Guide Figure D–2 off bit 0 Template 01 - Last Failure Event Sense Data Response Format 7 6 5 Unusd 1 2 4 3 2 1 0 Error Code Unused Sense Key Unused 3-6 Unused 7 Additional Sense Length 8-11 Unused 12 Additional Sense Code (ASC) 13 Additional Sense Code Qualifier (ASCQ) 14 Unused 15–17 Unused 18–31 Reserved 32-35 Instance Code 36 Template 37 Template Flags 38–53 Reserved 54–69 Controller Board Serial Number 70–73 Controller Software Revision Level
Event Reporting: Templates and Codes D–5 Multiple-Bus Failover Event Sense Data Response The HSG80 SCSI Host Interconnect Services software component reports Multiple Bus Failover events via the Multiple Bus Failover Event Sense Data Response (see Figure D–3). n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18. ASC and ASCQ codes (byte offsets 12 and 13) are described in Table D–7, “ASC and ASCQ Codes” on page D–85.
D–6 HSG80 User’s Guide Failover Event Sense Data Response The HSG80 controller Failover Control software component reports errors and other conditions encountered during redundant controller communications and failover operation via the Failover Event Sense Data Response (see Figure D–4). n n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18. ASC and ASCQ codes (byte offsets 12 and 13) are described in Table D–7, “ASC and ASCQ Codes” on page D–85.
Event Reporting: Templates and Codes Figure D–4 off bit 0 Template 05 - Failover Event Sense Data Response Format 7 6 5 Unusd 4 3 2 1 0 Error Code 1 2 D–7 Unused Unused Sense Key 3–6 Unused 7 Additional Sense Length 8–11 Unused 12 Additional Sense Code (ASC) 13 Additional Sense Code Qualifier (ASCQ) 14 Unused 15–17 Unused 18–31 Reserved 32–35 Instance Code 36 Template 37 Template Flags 38–53 Reserved 54–69 Controller Board Serial Number 70–73 Controller Software R
D–8 HSG80 User’s Guide Nonvolatile Parameter Memory Component Event Sense Data Response The HSG80 controller Executive software component reports errors detected while accessing a Nonvolatile Parameter Memory Component via the Nonvolatile Parameter Memory Component Event Sense Data Response (see Figure D–5). n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18.
Event Reporting: Templates and Codes D–9 Backup Battery Failure Event Sense Data Response The HSG80 controller Value Added Services software component reports backup battery failure conditions for the various hardware components that use a battery to maintain state during power failures via the Backup Battery Failure Event Sense Data Response (see Figure D–6). n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18.
D–10 HSG80 User’s Guide Subsystem Built-In Self Test Failure Event Sense Data Response The HSG80 controller Subsystem Built-In Self Tests software component reports errors detected during test execution via the Subsystem Built-In Self Test Failure Event Sense Data Response (see Figure D–7). n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18. ASC and ASCQ codes (byte offsets 12 and 13) are described in Table D–7, “ASC and ASCQ Codes” on page D–85.
Event Reporting: Templates and Codes Figure D–7 off D–11 Template 13 - Subsystem Built-In Self Test Failure Event Sense Data Response Format bit 0 7 6 5 Unusd 1 2 4 3 2 1 0 Error Code Unused Unused Sense Key 3-6 Unused 7 Additional Sense Length 8-11 Unused 12 Additional Sense Code (ASC) 13 Additional Sense Code Qualifier (ASCQ) 14 Unused 15–17 Unused 18–31 Reserved 32-35 Instance Code 36 Template 37 Template Flags 38–53 Reserved 54–69 Controller Board Serial Number
D–12 HSG80 User’s Guide Memory System Failure Event Sense Data Response The HSG80 controller Memory Controller Event Analyzer software component and the Cache Manager, part of the Value Added software component, report the occurrence of memory errors via the Memory System Failure Event Sense Data Response (see Figure D–8). n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18.
Event Reporting: Templates and Codes D–13 Device Services Non-Transfer Error Event Sense Data Response The HSG80 controller Device Services software component reports errors detected while performing non-transfer work related to disk (including CD-ROM and optical memory) device operations via the Device Services Non-Transfer Event Sense Data Response (see Figure D–9). n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18.
D–14 HSG80 User’s Guide Disk Transfer Error Event Sense Data Response The HSG80 controller Device Services and Value Added Services software components report errors detected while performing work related to disk (including CD-ROM and optical memory) device transfer operations via the Disk Transfer Error Event Sense Data Response (see Figure D–10). n n Instance Codes (byte offset 32-35) are described in Table D–1, “Instance Codes” on page D–18.
Event Reporting: Templates and Codes D–15 Figure D–10 Template 51 - Disk Transfer Error Event Sense Data Response Format off bit 7 6 5 0–17 4 3 2 18–19 Reserved 20 Total Number of Errors 21 Total Retry Count 22–25 ASC/ASCQ Stack 26–28 Device Locator 29–31 Reserved 32–35 Instance Code 36 Template 37 Template Flags 38 Reserved 39 Command Opcode 40 Sense Data Qualifier 41–50 Original CDB 51 Host ID 52–53 Reserved 54–69 Controller Board Serial Number 70–73 Controller
D–16 HSG80 User’s Guide Instance Codes An Instance Code is a number that uniquely identifies an event being reported. Instance Code Structure Figure D–11 shows the structure of an instance code. If you understand its structure, you will be able to translate it, bypassing the fault management utility (FMU).
Event Reporting: Templates and Codes D–17 NR Threshold Located at byte offset {8}32, the NR Threshold is the notification/ recovery threshold assigned to the event. This value is used during Symptom-Directed Diagnosis procedures to determine when notification/recovery action should be taken. Repair Action The Repair Action found at byte offset {9}33 indicates the recommended repair action code assigned to the event.
D–18 HSG80 User’s Guide Table D–1 contains the instance codes that can be issued by the controller’s fault-management software. Table D–1 Instance Codes Instance Description Code 01010302 An unrecoverable hardware detected fault occurred. 0102030A An unrecoverable software inconsistency was detected or an intentional restart or shutdown of controller operation was requested. 01032002 Nonvolatile parameter memory component EDC check failed; content of the component reset to default settings.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code The wrong write cache module is configured. The serial numbers do not match. Either the existing or the expected cache contains dirty write020D2401 back cached data. Note that in this instance the Memory Address, Byte Count, FX Chip Register, Memory Controller register, and Diagnostic register fields are undefined. The write cache module is missing.
D–20 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code The device specified in the Device Locator has transitioned from 022C0064 Copying or Normalizing state to Normal state. The device specified in the Device Locator field has been converted to a 022E0064 Mirrorset associated with the logical unit. The mirrored device specified in the Device Locator field has been 022F0064 converted to a single device associated with the logical unit.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code The write cache module which is the mirror for the primary cache is unexpectedly not present (missing). A cache is expected to be 02492401 configured and it may contain dirty write cached data. Note that in this instance, the Memory Address, Byte Count, FX Chip register, Memory Controller register, and Diagnostic register fields are undefined.
D–22 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code The write operation failed because the unit is Data Safety Write 0256000A Protected. The Information field of the Device Sense Data contains the block number of the first block in error. An attempt to reassign a bad disk block failed. The contents of the disk 0257000A block is lost. The Information field of the Device Sense Data contains the block number of the first block in error.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code Memory diagnostics performed during controller initialization detected 02613801 that the DIMM in location 1 failed on the cache module. Note that in this instance the Byte Count field in undefined. Memory diagnostics performed during controller initialization detected 02623801 that the DIMM in location 2 failed on the cache module. Note that in this instance the Byte Count field in undefined.
D–24 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code The device specified in the Device Locator field has been reduced from the Mirrorset associated with the logical unit. The nominal number of 026E0001 members in the mirrorset has been decreased by one. The reduced device is now available for use. The device specified in the Device Locator field failed to be added to the 026F530A mirrorset associated with the logical unit. The device will remain in the Spareset.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code The CACHEB0 Memory Controller failed Cache Diagnostics testing performed on the other cache during a cache failover attempt. The 027A2201 Memory Address field contains the starting physical address of the CACHEB0 memory. The CACHEB1 Memory Controller failed Cache Diagnostics testing performed on the other cache during a cache failover attempt.
D–26 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code The CACHE backup battery is near its end of life. The Memory Address 02892301 field contains the starting physical address of the CACHEA0 memory. The CACHE backup battery covering the mirror cache is near its end of 028A2301 life. The Memory Address field contains the starting physical address of the CACHEB1 memory. No command control structures available for disk operation.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code Nonvolatile memory and drive metadata indicate conflicting drive 0311430A configurations. The Synchronous Transfer Value differs between drives in the same 0312430A storageset. 03134002 Maximum number of errors for this data transfer operation exceeded. 03144002 Drive reported recovered error without transferring all data. 03154002 Data returned from drive is invalid.
D–28 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code During device initialization the maximum number of errors for a data 03374002 transfer operation was exceeded. 03384002 Request Sense command to the device failed. 03394002 Command timeout. 033A4002 Disconnect timeout. 033B4002 Unexpected bus phase. 033C4002 The device unexpectedly disconnected from the SCSI bus. 033D4002 Unexpected message. 033E4002 Message Reject received on a valid message.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code Device port SCSI chip reported gross error during operation to a device which is unknown to the controller. Note that in this instance the 03CD2002 Associated Additional Sense Code and Associated Additional Sense Code Qualifier fields are undefined. Non-SCSI bus parity error during operation to a device which is unknown to the controller.
D–30 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code During device initialization, the device reported the SCSI Sense Key MEDIUM ERROR. This indicates that the command terminated with a non-recovered error condition that was probably caused by a flaw in the 03D6450A medium or an error in the recorded data. This sense key may also be returned if the target is unable to distinguish between a flaw in the medium and a specific hardware failure (HARDWARE ERROR sense key).
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code During device initialization, the device reported the SCSI Sense Key ABORTED COMMAND. This indicates the target aborted the 03DE450A command. The initiator may be able to recover by trying the command again. During device initialization, the device reported the SCSI Sense Key 03DF450A EQUAL. This indicates a SEARCH DATA command has satisfied an equal comparison.
D–32 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code The SWAP interrupts have been cleared and re-enabled for all device ports. Note that in this instance the Associated Port, Associated Target, 03F20064 Associated Additional Sense Code, and Associated Additional Sense Code Qualifier fields are undefined. An asynchronous SWAP interrupt was detected by the controller for the device port indicated by the Associated Port field.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code The EMU has detected an elevated temperature condition. Note that in 03FA0D01 this instance the Associated Target, Associated Additional Sense Code, and Associated Additional Sense Code Qualifier fields are undefined. The EMU has detected an external air sense fault.
D–34 HSG80 User’s Guide Table D–1 Instance Codes (Continued) Instance Description Code Failover Control was unable to send keepalive communication to the other controller. It is assumed that the other controller is hung or not 07080B0A started. Note that in this instance the Last Failure Code and Last Failure Parameters fields are undefined.
Event Reporting: Templates and Codes Table D–1 Instance Codes (Continued) Instance Description Code The Quadrant 3 Memory Controller (CACHEB1) detected a Firewall 0C433E02 error. Host Port Protocol component has detected that the other controller has 43010064 failed and that this controller has taken over the units specified in the extended sense data. Host Port Protocol component has detected that this controller has taken 43020064 over (failed back) the units specified in the extended sense data.
D–36 HSG80 User’s Guide Last Failure Codes A Last Failure Code is a number that uniquely-describes an unrecoverable condition. It is found at byte offset 104 to 107 and will only appear in Figure D–2, “Template 01 - Last Failure Event Sense Data Response Format” on page D–4, and Figure D–4, “Template 05 Failover Event Sense Data Response Format” on page D–7. Last Failure Code Structure Figure D–13 shows the structure of a Last Failure Code.
Event Reporting: Templates and Codes D–37 HW This hardware/software flag is located at byte offset 104, bit 7. If this flag is equal to 1, the unrecoverable condition is due to a hardwaredetected fault. If this flag is equal to 0, the unrecoverable condition is due to an inconsistency with the software, or an intentional restart or shutdown of the controller was requested.
D–38 HSG80 User’s Guide Component IDs A component ID uniquely identifies the software component that detected the event and is found at byte offset {11}35 (see “Component Identifier Codes,” page D–82). Table D–3 contains the last failure codes that can be issued by the controller’s fault-management software. Table D–3 Last Failure Codes Code Description 01000100 Memory allocation failure during executive initialization. 01010100 An interrupt without any handler was triggered.
Event Reporting: Templates and Codes Table D–3 Code D–39 Last Failure Codes (Continued) Description 010E0110 All structures contained in the System Information Page (SIP) and the Last Failure entries have been reset to their default settings. This is a normal occurrence for the first boot following manufacture of the controller module and during the transition from one software version to another if and only if the format of the SIP is different between the two versions.
D–40 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 01160108 The I960 reported a machine fault (parity error). n Last Failure Parameter [0] contains the RESERVED value. n Last Failure Parameter [1] contains the access type value. n Last Failure Parameter [2] contains the access address value. n Last Failure Parameter [3] contains the number of faults value. n Last Failure Parameter [4] contains the PC value. n Last Failure Parameter [5] contains the AC value.
Event Reporting: Templates and Codes Table D–3 D–41 Last Failure Codes (Continued) Code Description 011C0011 Controller execution terminated via display of solid fault code in OCP LEDs. Note that upon receipt of this Last Failure in a last gasp message the other controller in a dual controller configuration will inhibit assertion of the KILL line. n Last Failure Parameter [0] contains the OCP LED solid fault code value. 018000A0 A powerfail interrupt occurred.
D–42 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 01910084 A Cache Module was inserted or removed. n Last Failure Parameter [0] contains the value of actual Cache Module A exists state. n Last Failure Parameter [1] contains the value of actual Cache Module B exists state. n Last Failure Parameter [2] contains the value of expected Cache Module A exists state. n Last Failure Parameter [3] contains the value of expected Cache Module B exists state.
Event Reporting: Templates and Codes Table D–3 Code D–43 Last Failure Codes (Continued) Description 01950188 An error has occurred that caused the FX to be rest, when not permissible. n Last Failure Parameter [0] contains the value of read diagnostic register 0. n Last Failure Parameter [1] contains the value of read diagnostic register 1. n Last Failure Parameter [2] contains the value of write diagnostic register 0. n Last Failure Parameter [3] contains the value of write diagnostic register 1.
D–44 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 01992088 An error was detected by the PLX. n Last Failure Parameter [0] contains the value of read diagnostic register 0. n Last Failure Parameter [1] contains the value of read diagnostic register 1. n Last Failure Parameter [2] contains the value of write diagnostic register 0. n Last Failure Parameter [3] contains the value of write diagnostic register 1.
Event Reporting: Templates and Codes Table D–3 Code D–45 Last Failure Codes (Continued) Description 022C0100 A READ_LONG operation was requested for a Local Buffer Transfer. READ_LONG is not supported for Local Buffer Transfers. 022D0100 A WRITE_LONG operation was requested for a Local Buffer Transfer. WRTE_LONG is not supported for Local Buffer Transfers. 023A2084 A processor interrupt was generated by the controller’s XOR engine (FX), indicating an unrecoverable error condition.
D–46 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 027B0102 An invalid status was returned from VA$XFER() in a complex ACCESS operation. n Last Failure Parameter[0] contains the DD address. n Last Failure Parameter[1] contains the invalid status. 027D0100 Unable to allocate memory for a Failover Control Block. 027E0100 Unable to allocate memory for a Failover Control Block. 027F0100 Unable to allocate memory for a Failover Control Block.
Event Reporting: Templates and Codes Table D–3 D–47 Last Failure Codes (Continued) Code Description 029A0100 Invalid cache buffer metadata detected while scanning the Buffer Metadata Array. Found a page containing dirty data but the corresponding Device Correlation Array entry does exist. 029D0100 Invalid metadata combination detected in build_bad_raid_node. 029F0100 The Cache Manager software has insufficient resources to handle a buffer request pending.
D–48 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 02AD0180 The FX detected a compare error for data that was identical. This error has always previously occurred due to a hardware problem. 02AE0100 The mirrorset member count and individual member states are inconsistent. Discovered during a mirrorset write or erase. 02AF0102 An invalid status was returned from VA$XFER() in a write operation. n Last Failure Parameter[0] contains the DD address.
Event Reporting: Templates and Codes Table D–3 D–49 Last Failure Codes (Continued) Code Description 02C70100 Bad BBR offsets for active shadowset, detected on write. 02C80100 Bad BBR offsets for active shadowset, detected on read. 02C90100 Illegal call made to CACHE$PURGE_META when the storageset was not quiesced. 02CA0100 Illegal call made to VA$RAID5_META_READ when another read (of metadata) is already in progress on the same strip. 02CB0000 A restore of the configuration has been done.
D–50 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 02E11016 While attempting to restore saved configuration information, data for two unrelated controllers was found. The restore code is unable to determine which disk contains the correct information. The Port/Target/LUN information for the two disks is contained in the parameter list.
Event Reporting: Templates and Codes Table D–3 Last Failure Codes (Continued) Code 02EF0102 D–51 Description A CLD is free when it should be allocated. n Last Failure Parameter [0] contains the requesting entity. n Last Failure Parameter [1] contains the CLD index. 02F00100 The controller has insufficient free resources for the configuration restore process to obtain a facility lock. 02F10102 The configuration restore process encountered an unexpected non-volatile parameter store format.
D–52 HSG80 User’s Guide Table D–3 Code 02F60103 Last Failure Codes (Continued) Description An invalid modification to the no_interlock VSI flag was attempted. n Last Failure Parameter [0] contains the nv_index of the config on which the problem was found. n Last Failure Parameter [1] contains modification flag. n Last Failure Parameter [2] contains the current value of the no_interlock flag.
Event Reporting: Templates and Codes Table D–3 D–53 Last Failure Codes (Continued) Code Description 02FC0180 The FX detected a compare error for data that was identical. This error has always previously occurred due to a hardware problem. 02FD0100 The controller has insufficient free memory to restore saved configuration information from disk. 02FE0105 A field in the VSI was not cleared when an attempt was made to clear the interlock.
D–54 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 030B0188 A dip error was detected when pcb_busy was set. n Last Failure Parameter [0] contains the PCB port_ptr value. n Last Failure Parameter [1] contains the new info NULL-SSTAT0-DSTAT-ISTAT. n Last Failure Parameter [2] contains the PCB copy of the device port DBC register. n Last Failure Parameter [3] contains the PCB copy of the device port DNAD register.
Event Reporting: Templates and Codes Table D–3 Code D–55 Last Failure Codes (Continued) Description 03330188 A parity error was detected by a device port while sending data out onto the SCSI bus. n Last Failure Parameter [0] contains the PCB port_ptr value. n Last Failure Parameter [1] contains the PCB copy of the device port TEMP register. n Last Failure Parameter [2] contains the PCB copy of the device port DBC register.
D–56 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 03370108 A device port detected an illegal script instruction. n Last Failure Parameter [0] contains the PCB port_ptr value. n Last Failure Parameter [1] contains the PCB copy of the device port TEMP register. n Last Failure Parameter [2] contains the PCB copy of the device port DBC register. n Last Failure Parameter [3] contains the PCB copy of the device port DNAD register.
Event Reporting: Templates and Codes Table D–3 Code D–57 Last Failure Codes (Continued) Description 03390108 An unknown interrupt code was found in a device port’s DSPS register. n Last Failure Parameter [0] contains the PCB port_ptr value. n Last Failure Parameter [1] contains the PCB copy of the device port TEMP register. n Last Failure Parameter [2] contains the PCB copy of the device port DBC register. n Last Failure Parameter [3] contains the PCB copy of the device port DNAD register.
D–58 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 033F0108 An EDC error was detected on a read of a soft-sectored device path not yet implemented. n Last Failure Parameter [0] contains the PCB port_ptr value. n Last Failure Parameter [1] contains the PCB copy of the device port TEMP register. n Last Failure Parameter [2] contains the PCB copy of the device port DBC register. n Last Failure Parameter [3] contains the PCB copy of the device port DNAD register.
Event Reporting: Templates and Codes Table D–3 D–59 Last Failure Codes (Continued) Code Description 034A0100 Insufficient memory available for PUB allocation. 034B0100 Insufficient memory available for DS init buffer allocation. 034C0100 Insufficient memory available for static structure allocation. 034D0100 DS init DWDs exhausted. 034E2080 Diagnostics report all device ports are broken. 034F0100 Insufficient memory available for reselect target block allocation.
D–60 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 03980100 Failed to allocate expandable EMU static work structures. 03990100 Failed to allocate expandable EMU work entry. 039A0100 Failed to allocate expandable EMU FOC work entry. 039B0100 EMU request work queue corrupted. 039C0100 EMU response work queue corrupted. 039D0100 EMU work queue corrupted. 039E0100 EMU foc request work queue corrupted. 039F0100 EMU foc response work queue corrupted.
Event Reporting: Templates and Codes Table D–3 D–61 Last Failure Codes (Continued) Code Description 04030102 The USB index supplied in the Event Information Packet (EIP) is larger than the maximum number of USBs. n Last Failure Parameter[0] contains the instance code value. n Last Failure Parameter[1] contains the USB index value. 04040103 The event log format found in V_fm_template_table is not supported by the Fault Manager.
D–62 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 05010100 In recursive_nonconflict could not get enough memory for scanning the keyword tables for configuration name conflicts. 06010100 The DUART was unable to allocate enough memory to establish a connection to the CLI. 06020100 A port other than terminal port A was referred to by a set terminal characteristics command. This is illegal.
Event Reporting: Templates and Codes Table D–3 Code D–63 Last Failure Codes (Continued) Description 08020100 No memory could be allocated for a NVFOC information packet. 08030101 Work received on the S_nvfoc_bque did not have a NVFOC work id. n Last Failure Parameter[0] contains the id type value that was received on the NVFOC work queue. 08040101 Unknown work value received by the S_nvfoc_bque. n Last Failure Parameter[0] contains the unknown work value.
D–64 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 08170100 A request to read the next configuration was received but the memory was not locked. 08180100 Could not get enough memory for FLS FCBs to receive information from the other controller. 08190100 An unlock command was received when the NV memory was not locked. 081A0100 Unable to allocate memory for remote work. 081B0101 Bad remote work received on remote work queue.
Event Reporting: Templates and Codes Table D–3 Last Failure Codes (Continued) Code Description 09C80101 Remote FLM detected an invalid facility to act upon. n Last Failure Parameter [0] contains the facility found. 09C90101 Remote FLM detected an invalid work type. n Last Failure Parameter [0] contains the work type found. 09CA0101 Remote FLM detected an invalid work type. Last Failure Parameter [0] contains the work type found.
D–66 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 0A140100 New entry pointer is not properly aligned. 0A150100 New entry record type is out of range. 0A190102 ilf_depopulate_DWD_to_cache first page guard check failed. Last Failure Parameter [0] contains the DWD address value Last Failure Parameter [1] contains the buffer address value. n n 0A1C0102 ILF$LOG_ENTRY page guard check failed.
Event Reporting: Templates and Codes Table D–3 D–67 Last Failure Codes (Continued) Code Description 0A2D0100 ilf_populate_DWD_from_cache buffer stack entry zero or not page aligned. 0A2E0100 ilf_populate_DWD_from_cache returned buffer type not IDX_ILF. 0A2F0100 ilf_rebind_cache_buffs_to_DWDs buffer stack entry not page aligned. 0A300100 ilf_depopulate_DWD_to_cache buffer stack entry zero or not page aligned. 0A310100 ilf_distribute_cache_DWDs active handle count not as expected.
D–68 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 0D000011 The EMU firmware returned a bad status when told to poweroff. n Last Failure Parameter [0] contains the value of the bad status. 12000103 Two values found not equal. n Last Failure Parameter [0] contains the ASSUME instance address. n Last Failure Parameter [1] contains the first variable value. n Last Failure Parameter [2] contains the second variable value. 12010103 Two values found equal.
Event Reporting: Templates and Codes Table D–3 Code D–69 Last Failure Codes (Continued) Description 12080102 vsi_ptr->cs_interlocked not set. n Last Failure Parameter [0] contains the ASSUME instance address. n Last Failure Parameter [1] contains nv_index value. 12090102 Unhandled switch case. n Last Failure Parameter [0] contains the ASSUME instance address. n Last Failure Parameter [1] contains nv_index value.
D–70 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 20100101 A config_node of type VA_MA_DEVICE had an unrecognized SCSI device type. n Last Failure Parameter[0] contains the SCSI device type number that was unrecognized. 20110100 An attempt to allocate memory so the CLI prompt messages could be deleted failed. 20120101 While traversing the structure of a unit, a config_info node was discovered with an unrecognized structure type.
Event Reporting: Templates and Codes Table D–3 D–71 Last Failure Codes (Continued) Code Description 20240000 A restart of both controllers is required when entering multibus failover. 20260000 With “set failover copy=other”, the controller which is having the configuration copied to will automatically be restarted via this bugcheck. 20640000 Nindy was turned on. 20650000 Nindy was turned off. 20692010 To enter dual-redundant mode, both controllers must be of the same type.
D–72 HSG80 User’s Guide Table D–3 Last Failure Codes (Continued) Code Description 44640100 Not enough abort requests in the system. 44650100 Exceeded the number of SEST abort retries. 44660100 Unable to allocate enough abort requests for Fibre Channel Host Port Transport software layer. 44670100 Unable to allocate enough command HTBs for Fibre Channel Host Port Transport software layer. 44680100 Unable to allocate enough FC HTBs for Fibre Channel Host Port Transport software layer.
Event Reporting: Templates and Codes Table D–3 Code D–73 Last Failure Codes (Continued) Description 44760100 The Host Port Transport ran out of work requests. 44770102 An illegal script return value was received by the Host Port Transport init script handler. n Last Failure Parameter [0] contains the init function. n Last Failure Parameter [1] contains return value. The Host Port Transport ran out of work requests.
D–74 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 447F0100 The Host Port Transport memory for LOGI parameters. 44800101 An illegal status was returned to the name service command error handler. n Last Failure Parameter [0] contains error value. 44810101 An illegal status was returned to the PLOGI command error handler. n Last Failure Parameter [0] contains error value. 44820101 An illegal abort type was given to the Host Port Transport abort handler.
Event Reporting: Templates and Codes Table D–3 Code D–75 Last Failure Codes (Continued) Description 80050100 DILX tried to change the usb unit state from MAINTENANCE_MODE to NORMAL but DILX never received notification of a successful state change. 80060100 DILX tried to switch the unit state from MAINTENANCE_MODE to NORMAL but was not successful. 80070100 DILX aborted all cmds via va$d_abort() but the HTBS haven’t been returned.
D–76 HSG80 User’s Guide Table D–3 Code Last Failure Codes (Continued) Description 84010100 An unsupported message type or terminal request was received by the CLONE virtual terminal code from the CLI. 85010100 HSUTIL tried to release a facility that wasn’t reserved by HSUTIL. 85020100 HSUTIL tried to change the unit state from MAINTENANCE_MODE to NORMAL but was rejected because of insufficient resources.
Event Reporting: Templates and Codes D–77 Recommended Repair Action Codes Recommended Repair Action Codes are embedded in Instance and Last Failure codes. Refer to “Instance Codes,” page D–16, and “Last Failure Codes,” page D–36, for a more detailed description of the relationship between these codes. Table D–4 contains the repair action codes assigned to each significant event in the system. Table D–4 Recommended Repair Action Codes Code Description 00 No action necessary.
D–78 HSG80 User’s Guide Table D–4 Recommended Repair Action Codes (Continued) Code 0B Description The other controller in a dual-redundant configuration has been reset with the “Kill” line by the controller that reported the event. To restart the “Killed” controller enter the CLI command RESTART OTHER on the “Surviving” controller and then depress the (//) RESET button on the “Killed” controller.
Event Reporting: Templates and Codes Table D–4 D–79 Recommended Repair Action Codes (Continued) Code Description 24 Check for the following invalid write cache configurations: n If the wrong write cache module is installed, replace with the matching module or clear the invalid cache error via the CLI. Refer to Appendix B, “CLI Commands” for more information.
D–80 HSG80 User’s Guide Table D–4 Code Recommended Repair Action Codes (Continued) Description 40 If the Sense Data FRU field is non-zero, follow repair action 41. Otherwise, replace the appropriate FRU associated with the device’s SCSI interface or the entire device. 41 Consult the device’s maintenance manual for guidance on replacing the indicated device FRU. 43 Update the configuration data to correct the problem. 44 Replace the SCSI cable for the failing SCSI bus.
Event Reporting: Templates and Codes Table D–4 D–81 Recommended Repair Action Codes (Continued) Code Description 56 Perform the repair actions indicated in any and all event reports found for the member device that was removed from the STORAGESET. Then perform repair action 57. 57 Delete the device from the FAILEDSET and redeploy, perhaps by adding it to the SPARESET so it will be available to be used to replace another failing device.
D–82 HSG80 User’s Guide Component Identifier Codes Component Identifier Codes are embedded in Instance and Last Failure codes. Refer to “Instance Codes,” page D–16, and “Last Failure Codes,” page D–36, for a more detailed description of the relationship between these codes. Table D–5 lists the component identifier codes.
Event Reporting: Templates and Codes Table D–5 Component Identifier Codes (Continued) Code Description 82 Subsystem Built-In Self Tests (BIST) 83 Device Configuration Utilities (CONFIG) 84 Clone Unit Utility (CLONE) 85 Format and Device Code Load Utility (HSUTIL) 86 Code Load/Code Patch Utility (CLCP) 8A Field Replacement Utility (FRUTIL) 8B Periodic Diagnostics (PDIAG) D–83
D–84 HSG80 User’s Guide Event Threshold Codes Table D–6 lists the classifications for event notification and recovery threshold values. Table D–6 Event Notification/Recovery Threshold Classifications Threshold Value Classification Description 01 IMMEDIATE Failure or potential failure of a component critical to proper controller operation is indicated; immediate attention is required.
Event Reporting: Templates and Codes D–85 ASC/ASCQ Codes Table D–7 lists HSG80-specific SCSI ASC and ASCQ codes. These codes are Template-specific and appear at byte offsets 12 and 13. Note Additional codes that are common to all SCSI devices can be found in the SCSI specification. Table D–7 ASC and ASCQ Codes ASC Code ASCQ Code Description 04 80 Logical unit is disaster tolerant failsafe locked (inoperative).
D–86 HSG80 User’s Guide Table D–7 ASC and ASCQ Codes (Continued) ASC Code ASCQ Code Description A0 02 Backup battery failure event report. A0 03 Subsystem built-in self test failure event report. A0 04 Memory system failure event report. A0 05 Failover event report. A0 07 RAID membership event report. A0 08 Multiple Bus failover event. A0 09 Multiple Bus failback event. A0 0A Disaster Tolerance failsafe error mode can now be enabled. A1 00 Shelf OK is not properly asserted.
Event Reporting: Templates and Codes Table D–7 ASC and ASCQ Codes (Continued) ASC Code ASCQ Code Description D0 01 Disconnect timeout. D0 02 Chip command timeout. D0 03 Byte transfer timeout. D1 00 Bus errors. D1 02 Unexpected bus phase. D1 03 Disconnect expected. D1 04 ID Message not sent. D1 05 Synchronous negotiation error. D1 07 Unexpected disconnect. D1 08 Unexpected message. D1 09 Unexpected Tag message. D1 0A Channel busy.
E–1 APPENDIX E Controller Specifications This appendix contains physical, electrical, and environmental specifications for the HSG80 array controller.
E–2 HSG80 User’s Guide Physical and Electrical Specifications for the Controller Table E–1 lists the physical and electrical specifications for the controller and cache modules. Table E–1 Controller Specifications Hardware Length Width Power Current at +5 V HSG80 Array Controller module 12.5 inches 8.75 inches 23.27 W 6.04 A Write-back Cache, 512 MB 12.5 inches (Battery charging) 7.75 inches 2.48 W 8.
Controller Specifications E–3 Environmental Specifications The HSG80 array controller is intended for installation in a Class A computer room environment. The environmental specifications listed in Table E–2 are the same as for other DIGITAL storage devices.
G–1 Glossary This glossary defines terms pertaining to the HSG80 Fibre Channel array controller. It is not a comprehensive glossary of computer terms. 8B/10B A type of byte encoding and decoding to reduce errors in data transmission patented by the IBM Corporation. This process of encoding and decoding data for transmission has been adopted by ANSI. adapter A device that converts the protocol and hardware interface of one bus type into another without changing the function of the bus.
G–2 HSG80 User’s Guide array controller software Abbreviated ACS. Software contained on a removable ROM program card that provides the operating system for the array controller. asynchronous Pertaining to events that are scheduled as the result of a signal asking for the event; pertaining to that which is without any specified time relation. See also synchronous. autospare A controller feature that automatically replaces a failed disk drive.
Glossary G–3 byte A binary character string made up of 8 bits operated on as a unit. cache memory A portion of memory used to accelerate read and write operations. CCITT Acronym for Consultive Committee International Telephone and Telegraph. An international association that sets worldwide communication standards, recently renamed International Telecommunications Union (ITU). CDU Cable distribution unit. The power entry device for StorageWorks cabinets.
G–4 HSG80 User’s Guide container 1) Any entity that is capable of storing data, whether it is a physical device or a group of physical devices. (2) A virtual, internal controller structure representing either a single disk or a group of disk drives linked as a storageset. Stripesets and mirrorsets are examples of storageset containers the controller uses to create units.
Glossary G–5 differential SCSI bus A bus in which a signal’s level is determined by the potential difference between two wires. A differential bus is more robust and less subject to electrical noise than is a single-ended bus. DIMM Dual inline Memory Module. dirty data The write-back cached data that has not been written to storage media, even though the host operation processing the data has completed. DMA Direct Memory Access. DOC DWZZA-On-a-Chip.
G–6 HSG80 User’s Guide EMU Environmental monitoring unit. A unit that provides increased protection against catastrophic failures. Some subsystem enclosures include an EMU which works with the controller to detect conditions such as failed power supplies, failed blowers, elevated temperatures, and external air sense faults. The EMU also controls certain cabinet hardware including DOC chips, alarms, and fan speeds. ESD Electrostatic discharge.
Glossary G–7 FC–PH The Fibre Channel Physical and Signaling standard. FC–SB Fibre Channel Single Byte Command Code Set FC–SW Fibre Channel Switched Topology and Switch Controls FCC Federal Communications Commission. The federal agency responsible for establishing standards and approving electronic devices within the United States. FCC Class A This certification label appears on electronic devices that can only be used in a commercial environment within the United States.
G–8 HSG80 User’s Guide FRU Field replaceable unit. A hardware component that can be replaced at the customer’s location by DIGITAL service personnel or qualified customer service personnel. full duplex (n) A communications system in which there is a capability for 2-way transmission and acceptance between two sites at the same time. full duplex (adj) Pertaining to a communications method in which data can be transmitted and received at the same time.
Glossary G–9 UNIX®, OpenVMS, Sun®, and Hewlett-Packard® HP–UX); B, IBM AIX®; C, Proprietary; and D, Microsoft Windows NTTM Server. 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.
G–10 HSG80 User’s Guide 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 visa versa), the actual transfer of the data, and the processing and overlaying activity to make both of those happen. IPI Intelligent Peripheral Interface.
Glossary G–11 logical unit A physical or virtual device addressable through a target ID number. LUNs use their target’s bus connection to communicate on the SCSI bus. logical unit number A value that identifies a specific logical unit belonging to a SCSI target ID number. A number associated with a physical device unit during a task’s I/O operations. Each task in the system must establish its own correspondence between logical unit numbers and physical devices. logon Also called login.
G–12 HSG80 User’s Guide metadata The data written to a disk for the purposes of controller administration. Metadata improves error detection and media defect management for the disk drive. It is also used to support storageset configuration and partitioning. Nontransportable disks also contain metadata to indicate they are uniquely configured for StorageWorks environments. Metadata can be thought of as “data about data.” mirroring The act of creating an exact copy or image of data.
Glossary G–13 nonredundant controller configuration (1) A single controller configuration. (2) A controller configuration that does not include a second controller. 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.
G–14 HSG80 User’s Guide 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. participating mode A mode within an L_Port that allows the port to participate in loop activities. A port must have a valid AL_PA to be in participating mode. PCM Polycenter Console Manager. PCMCIA Personal Computer Memory Card Industry Association.
Glossary port G–15 (1) In general terms, a logical channel in a communications system. (2) The hardware and software used to connect a host controller to a communications bus, such as a SCSI bus or serial bus. Regarding the controller, the port is (1) the logical route for data in and out of a controller that can contain one or more channels, all of which contain the same type of data. (2) The hardware and software that connects a controller to a SCSI device.
G–16 HSG80 User’s Guide 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. A single logical disk spans multiple physical disks, allowing parallel data processing for increased I/O performance. While the performance characteristics of RAID level 0 is excellent, this RAID level is the only one that does not provide redundancy.
Glossary G–17 RAM Random access memory. read ahead caching A caching technique for improving performance of synchronous sequential reads by prefetching data from disk. read caching A cache management method used to decrease the subsystem’s response time to a read request by allowing the controller to satisfy the request from the cache memory rather than from the disk drives. reconstruction The process of regenerating the contents of a failed member’s data.
G–18 HSG80 User’s Guide installed in a 3.5-inch or 5.25-inch carrier, whether it is a storage device or power supply. SCSI Small computer system interface. (1) An ANSI interface standard defining the physical and electrical parameters of a parallel I/O bus used to connect initiators to devices. (2) a processor-independent standard protocol for system-level interfacing between a computer and intelligent devices including hard drives, floppy disks, CD-ROMs, printers, scanners, and others.
Glossary G–19 service rate The rate at which an entity is able to service requests For example, the rate at which an Arbitrated Loop is able to service arbitrated requests. signal converter See SCSI bus signal converter. SIMM Single Inline Memory Module. single ended I/O module A 16-bit I/O module. See also I/O module. single-ended SCSI bus An electrical connection where one wire carries the signal and another wire or shield is connected to electrical ground.
G–20 HSG80 User’s Guide StorageWorks systems include integrated SBBs and array controllers to form storage subsystems. System-level enclosures to house the shelves and standard mounting devices for SBBs are also included. stripe The data divided into blocks and written across two or more member disks in an array. striped mirrorset See RAID level 0+1. stripeset See RAID level 0. stripe size The stripe capacity as determined by n–1 times the chunksize, where n is the number of RAIDset members.
Glossary G–21 topology An interconnection scheme that allows multiple Fibre Channel ports to communicate with each other. For example, point-to-point, Arbitrated Loop, and switched fabric are all Fibre Channel topologies. transfer data rate The speed at which data may be exchanged with the central processor, expressed in thousands of bytes per second. ULP Upper Layer Protocol.
G–22 HSG80 User’s Guide warm swap A device replacement method that allows the complete system remains online during device removal or insertion. The system bus may be halted, or quiesced, for a brief period of time during the warm-swap procedure. Worldwide name A unique 64-bit number assigned to a subsystem by the Institute of Electrical and Electronics Engineers (IEEE) and set by DIGITAL manufacturing prior to shipping. This name is referred to as the node ID within the CLI.
I–1 Index A AC input module part number, 1–3 Access door part number, 1–9 ADD DISK, B–11 NOTRANSPORTABLE, B–12 TRANSFER_RATE_REQUESTED, B–12 TRANSPORTABLE, B–12 ADD DISK container-name scsi-port-target-lun, B–11 ADD MIRRORSET, B–15 COPY, B–15 POLICY, B–16 READ_SOURCE, B–16 ADD RAIDSET, B–19 NOPOLICY, B–19 NOREDUCED, B–21 POLICY, B–19 RECONSTRUCT, B–20 REDUCED, B–21 ADD RAIDSET RAIDset-name containernameN, B–19 ADD SPARESET, B–23 ADD SPARESET disk-name, B–23 ADD STRIPESET, B–25 ADD STRIPESET stripeset-name
I–2 HSG80 User’s Guide Array Controller.
Index Cache, setting flush timer, B–105 CACHE_FLUSH_TIMER SET controller, B–105 CACHE_UPS SET controller, B–105 Caching techniques, 1–5 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, B–52 INITIALIZE, B–72 Caution, defined, xxi Change volume serial number utility.
I–4 HSG80 User’s Guide DELETE connections, B–55 DELETE container-name, B–57 DELETE FAILEDSET, B–59 DELETE SPARESET, B–61 DELETE unit-number, B–63 DESTROY_PARTITION, B–65 DIRECTORY, B–67 editing keys, B–4 getting help, B–3 HELP, B–69 INITIALIZE, B–71 LOCATE, B–77 MIRROR, B–79 overview, B–2 POWEROFF, B–83 REDUCE, B–85 RENAME, B–89 RETRY_ERRORS unit-number UNWRITEABLE_DATA, B–93 rules for entering, B–3 RUN, B–95 SELFTEST controller, B–99 SET controller, B–103 SET device-name, B–111 SET EMU, B–113 SET FAILEDS
Index CONFIGURATION RESET, B–45 CONFIGURATION RESTORE, B–47 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, B–49 Configuration utility.
I–6 HSG80 User’s Guide general description, 1–3 host ports, 1–13 installing dual-redundant controller configuration, 5–18 single-controller configuration, 5–4 local connection, 2–7 location, 1–13 maintenance features, 4–1 maintenance port, 1–13 multiple-bus failover configuration, 2–11 multiple-bus failover mode, 2–11 node IDs, 3–26 OCP, 1–13 patching controller software with the CLCP utility, 1–16 program card, 1–13 relationship to cache module, 1–13 release lever, 1–13 removing dual-redundant controller
Index single-disk units, B–33 sparesets, B–23 storageset and device profiles, 3–5 stripesets, B–25 units, B–27 CYLINDERS CREATE_PARTITION, B–52 INITIALIZE, B–72 D DAEMON tests, 4–42 Data backing up with the Clone utility, 1–16 duplicating with the Clone utility, 1–16 Data center cabinet ECB Y cable, 1–19, 1–28 Data patterns for DILX write test, 4–39 Data transfer rate, 3–49 Data-retention-policy CLEAR_ERRORS controller INVALID_CACHE, B–37 DELETE connections, B–55 DELETE container-name, B–57 DELETE FAILEDS
I–8 HSG80 User’s Guide mapping in subsystem, 4–25 maximum number in striped mirrorsets, 1–6, 2–2 maximum number supported, 1–5, 2–2 number per port, 1–5 renaming the volume serial number with the CHVSN utility, 1–17 replacing, 5–47 setting data transfer rate, B–12, B–111 SHOW device-type, B–144 showing, B–143 testing read and write capability, 4–38 testing read capability, 4–37 transfer rate, 3–46 upgrading firmware, 6–11 Diagnostics ECB charging, 1–29 listing of, B–67 running, B–95 DILX, 4–37 general des
Index Disk inline exerciser general description, 1–15 DISKS SHOW device-type, B–144 Display.
I–10 HSG80 User’s Guide replacing ECBs with FRUTIL, 1–16 replacing in a dual-redundant controller configuration, 5–27 replacing in a single-configuration controller, 5–27 replacing with cabinet powered off, 5–29 replacing with cabinet powered on, 5–28 single-battery ECB part number, 1–4, 1–28 single-controller configuration replacing with cabinet powered off, 5–29 replacing with cabinet powered on, 5–28 ECB Y cable BA370 enclosure part numbers, 1–19 data center cabinet part numbers, 1–19 part numbers, 1–2
Index FANSPEED SET EMU, B–114 Fault LEDs, 1–13 Fault management utility.
I–12 HSG80 User’s Guide G GLM copper part number, 1–9 installing, 5–33 installing in a dual-redundant controller configuration, 5–33 installing in a single-configuration controller, 5–33 optical part number, 1–11 removing, 5–32 removing in a dual-redundant controller configuration, 5–32 removing in a single-configuration controller, 5–32 replacing, 5–32 replacing in a dual-redundant controller configuration, 5–32 replacing in a single-configuration controller, 5–32 H HEADS CREATE_PARTITION, B–52 INITIALI
Index I/O module part number, 1–3 replacing, 5–39 replacing in a dual-redundant controller configuration, 5–39 replacing in a single-configuration controller, 5–39 IDENTIFIER SET controller, B–106 SET unit-number, B–139 IGNORE_ERRORS RESTART controller, B–91 SELFTEST controller, B–99 SHUTDOWN controller, B–149 IMMEDIATE_SHUTDOWN RESTART controller, B–91 SELFTEST controller, B–99 SHUTDOWN controller, B–149 INITIALIZE, B–71 CAPACITY, B–72 changing, 3–67 CHUNKSIZE, B–72 CYLINDERS, B–72 DESTROY, B–73 HEADS, B–
I–14 HSG80 User’s Guide single-controller configuration cache module, 5–7 controller, 5–4 DIMMs, 5–44 fibre cable, 5–45 GLM, 5–33 hub, 5–45 software patches, 6–6 Instance codes, D–18 to D–35 structure, 4–19 translating, 4–18 Interpreting event codes, 4–19 J JBOD, 3–8 L Largest device supported, 1–6, 2–2 Last failure codes list, D–38 to D–76 Last failure reporting events controller termination, 4–15 Last-failure codes displaying, 4–17 logging, 4–20 structure, 4–19 translating, 4–18 LED codes flashing pat
Index Map of devices in subsystem, 4–25 Mapping storagesets, 3–32 Maximum LUN capacity, 2–2 MAXIMUM_CACHED_TRANSFER ADD UNIT, B–29 SET unit-number, B–139 Mean time between failures, 3–10 Member replacing, 5–47 Members distributing first member of mirrorset, 3–13 distributing on bus, 3–13 to 3–14, 3–16 MEMBERSHIP SET mirrorset-name, B–121 Membership RAIDset switches, 3–41 Memory-system failures, 4–17 Metadata erasing, 3–65 retaining, 3–65 MIRROR, B–79 COPY, B–79 POLICY, B–80 MIRROR disk-name mirrorset-name,
I–16 HSG80 User’s Guide NOIDENTIFIER SET controller, B–106 SET unit-number, B–139 NOIGNORE_ERRORS RESTART controller, B–91 SELFTEST controller, B–99 SHUTDOWN controller, B–149 NOIMMEDIATE_SHUTDOWN RESTART controller, B–91 SELFTEST controller, B–99 SHUTDOWN controller, B–149 NOMIRRORED_CACHE SET controller, B–106 Nonvolatile memory fault-tolerance for write-back caching, 1–21 NOPOLICY ADD RAIDSET, B–19 NOPREFERRED_PATH ADD UNIT, B–30 SET unit-number, B–139 NOREAD_CACHE ADD UNIT, B–31 SET unit-number, B–140
Index fibre channel copper cable 10-meter, 1–9 5-meter, 1–9 fibre channel copper cabling parts used in configuring the controller, 1–9 fibre channel optical cable 10-meter, 1–11 20-meter, 1–11 2-meter, 1–11 30-meter, 1–11 50-meter, 1–11 5-meter, 1–11 fibre channel optical cabling parts used in configuring the controller, 1–11 GLM copper, 1–9 optical, 1–11 HSG80 subsystem, 1–3 I/O module, 1–3 maintenance port cable, 1–9 maintenance port cable for a terminal connection, 1–10 PC serial port adapter, 1–10 powe
I–18 HSG80 User’s Guide PORT_2_ALPA SET controller, B–107 PORT_2_TOPOLOGY SET controller, B–108 Ports See also Device ports, Host ports Power source enabling write-back caching, 1–21 Power supply part number, 1–4 Power, verification, and addressing module.
Index REDUCED, 3–41 replacement policy, 3–40 RAIDsets adding to configuration, B–19 adding while missing a member, B–21 changing characteristics, B–133 changing switches, 3–66 choosing chunk size, 3–47 configuring using CLI, 3–57 deleting, B–57 description, 3–2, 3–15 displaying information, B–143 initializing, B–71 maximum chunk size, 3–50 maximum membership, 3–16 planning, 3–16 removing a member, B–134 renaming, B–89 replacing a member, B–135 showing, B–143 specifying replacement policy, B–133 switches, 3
I–20 HSG80 User’s Guide fibre cable, 5–45 dual-redundant controller configuration, 5–45 single-controller configuration, 5–45 GLM, 5–32 hub, 5–45 dual-redundant controller configuration, 5–45 single-controller configuration, 5–45 single-controller configuration cache module, 5–6 controller, 5–3 DIMMs, 5–43 fibre cable, 5–45 GLM, 5–32 hub, 5–45 Removing a mirrorset member, B–85 RENAME, B–89 RENAME old-container-name new-containername, B–89 Renaming, B–89 Repair action codes list, D–77 to D–81 Repair-action
Index modules dual-redundant controller configuration, 5–8 modules in a single-controller configuration, 5–2 PCMCIA card, 5–46 PVA module, 5–34 first expansion enclosure, 5–36 master enclosure, 5–34 second expansion enclosure, 5–36 single-controller configuration, 5–2 cache module, 5–6 controller, 5–3 DIMMs, 5–42 ECB, 5–27 ECB with cabinet powered off, 5–29 ECB with cabinet powered on, 5–28 fibre cable, 5–45 GLM, 5–32 hub, 5–45 I/O module, 5–39 PCMCIA card, 5–46 PVA module, 5–34 PVA module, first expansion
I–22 HSG80 User’s Guide SCSI command operations, 4–18 SCSI device ports. See Device ports SCSI device targets. See Devices SCSI target ID numbers.
Index NORUN, B–140 NOWRITE_PROTECT, B–141 NOWRITEBACK_CACHE, B–141 PREFERRED_PATH, B–139 READ_CACHE, B–140 READAHEAD_CACHE, B–140 RUN, B–140 WRITE_PROTECT, B–141 WRITEBACK_CACHE, B–141 Setting cache flush timer, B–105 CLI prompt, B–108 control of metadata, B–73 controller behavior at restart, B–91 controller behavior at shutdown, B–149 controller behavior selftest, B–99 controller cache flush timer, B–105 controller cache UPS policy, B–105 controller configuration handling, B–73 controller error handling a
I–24 HSG80 User’s Guide Single-controller configuration connecting to the host using one hub, 2–14 ECB, 1–28 installing cache module, 5–7 controller, 5–4 DIMMs, 5–44 GLM, 5–33 removing cache module, 5–6 controller, 5–3 DIMMs, 5–43 GLM, 5–32 replacing cache module, 5–6 controller, 5–3 controller and its cache module, 5–2 DIMMs, 5–42 ECB, 5–27 ECB with cabinet powered off, 5–29 ECB with cabinet powered on, 5–28 GLM, 5–32 I/O module, 5–39 PCMCIA card, 5–46 PVA module, 5–34 PVA module in the first expansion e
Index creating map, 3–32 deleting, 3–65 displaying information, B–143 displaying switches, 3–66 dividing, 3–37 duplicating data with the Clone utility, 1–16 formatting disk drives with HSUTIL, 1–16 generating a new volume serial number with the CHVSN utility, 1–17 how they work with the host, 1–7 initializing, B–71 largest device supported, 1–6, 2–2 locating, B–77 maximum number of partitions supported, 2–2 mirrorsets, 3–2, 3–12 moving, 3–72 partitioning using CLI, 3–61 planning, 3–8 RAIDsets, 3–2 renaming
I–26 HSG80 User’s Guide Targets. See Devices Template, enclosure, A–4 Templates, D–85 Terminal setting parity, B–108 setting speed, B–109 Terminal connection optional maintenance port cable, 1–10, 2–7 part number for the optional maintenance port, 1–10 See also Maintenance port, Maintenance port cable Terminal display. See VTDPY Terminal.
Index See also Config utility See also HSUTIL Troubleshooting and maintaining the controller utilities and exercisers, 1–14 Turning off the subsystem, 5–48 Turning on the subsystem, 5–50 Typographical conventions, xx U Unit switches changing, 3–67 overview, 3–54 Units adding to configuration, B–27 changing characteristics, B–137 checking I/O, 4–29 checking status, 4–29 clearing lost data error, B–41 deleting from the configuration, B–63 displaying configured units, B–144 displaying information, B–143 exer
I–28 HSG80 User’s Guide renaming with the CHVSN utility, 1–17 VTDPY checking communication with host, 4–24 commands, 4–23 general description, 1–15, 4–23 running, 4–23 VTDPY, running, B–96 W Warning, defined, xxi Worldwide names, 3–26 Write capability, test for devices, 4–38 Write performance, 3–49 Write protection for program card, 6–4 WRITE_PROTECT ADD UNIT, B–32 SET unit-number, B–141 Write-back caching enabled for all disk units, 1–21 fault-tolerance, 1–21 general description, 1–21 setting the flush
