Document Outline

• Figures
• Tables
• Preface
• Precautions
  • Electrostatic Discharge Precautions
  • Component Precaution
  • Maintenance Port Precautions
• Conventions
  • Typographical Conventions
  • Special Notices
• Required Tools
• Related Publications
• Revision History
• chapter 1
  • General Description
  • The HSG80 Array Controller Subsystem
    • Figure 1–1 The HSG80 Subsystem
      • Table 1–1 Key to Figure 1–1The HSG80 Subsystem (Continued)
    • Summary of HSG80 Features
      • Table 1–2 Controller Features (Continued)
  • The HSG80 Array Controller
    • Figure 1–2 A Host and Its Storage Subsystem
    • Figure 1–3 HSG80 Array Controller Fibre Channel Copper Cabling
      • Table 1–3 Key to Figure 1–3 HSG80 Array Controller–Fibre Channel Copper Cabling
      • Figure 1–4 Optional Maintenance Port Cable for a Terminal Connection
      • Table 1–4 Key to Figure 1–4: Optional Maintenance Port Cable for a Terminal Connection
    • Figure 1–5 HSG80 Array Controller–Fibre Channel Optical Cabling
      • Table 1–5 Key to Figure 1–4 HSG80 Array Controller–Fibre Channel Optical cabling
    • Figure 1–6 Fibre Channel Optical Cleaning Procedures
      • Figure 1–7 Location of Controllers and Cache Modules
    • Operator Control Panel
      • Figure 1–8 HSG80 Controller Operator Control Panel (OCP)
    • Maintenance Port
    • Utilities and Exercisers
  • Cache Module
    • Table 1–6 Cache Module Memory Configurations
    • Figure 1–9 Cache Module
    • Caching Techniques
    • Fault-Tolerance for Write-Back Caching
      • Table 1-7 Cache Policies and Cache Module Status (Continued)
      • Table 1-8 Cache Policies Resulting and ECB Status (Continued)
  • External Cache Battery
    • Figure 1–10 ECB for Dual-Redundant Configurations
    • Table 1–9 ECB Capacity Based on Memory Size
    • Charging Diagnostics
• chapter 2
  • Configuring an HSG80 Array Controller
  • Introduction
    • Configuration Rules
  • Configuring an HSG80 Array Controller
  • Setting the PVA Module ID Switch
    • Figure 2–1 SCSI Target ID Numbers on the Controller Device Bus and PVA Settings in an Extended Su...
  • Establishing a Local Connection to the Controller
    • Figure 2–2 Terminal to Local-Connection Port Connection
    • Figure 2–3 “This Controller” and “Other Controller”
  • Selecting a Failover Mode
    • Using Transparent Failover
    • Using Multiple-Bus Failover
  • Enabling Mirrored Write-Back Cache
    • Selecting a Cache Mode
    • Fault-Tolerance
    • Backing up Power with a UPS
  • Connecting the Subsystem to the Host
    • Connecting a Single Controller to the Host Using One Hub
      • Figure 2–4 Cabling for Single Configuration with Fibre Channel Copper Support
        • Table 2–1 Key to Figure 2–4 Cabling for Single Configuration (copper)
      • Figure 2–5 Cabling for Single Configuration with Fibre Channel Optical Support
        • Table 2–2 Key to Figure 2–5 Cabling for Single Configuration (optical)
    • Connecting a Dual-Redundant Controller Configuration to the Host
      • Figure 2–6 Cabling for Dual-Redundant Configuration with Two Hubs using Fibre Channel Copper Support
        • Table 2–3 Key to Figure 2–6 Cabling for Dual-Redundant Configuration with Two Hubs (copper)
      • Figure 2–7 Cabling for Dual-Redundant Configuration with Two Hubs using Fibre Channel Optical Sup...
        • Table 2–4 Key to Figure 2–7 Cabling for Dual-Redundant Configuration with Two Hubs (optical)
        • Figure 2–8 Cabling for Dual-Redundant Configuration with One Hub using Fibre Channel Copper Support
        • Table 2–5 Key to Figure 2–8 Cabling for Dual-Redundant Configuration with One Hub using Fibre Cha...
      • Figure 2–9 Cabling for Dual-Redundant Configuration with One Hub using Fibre Channel Optical Support
        • Table 2–6 Key to Figure 2–9 Cabling for Dual-Redundant Configuration with One Hub using Fibre Cha...
• chapter 3
  • Creating Storagesets
  • Introduction
    • Figure 3–1 Units Created from Storagesets, Partitions, and Drives
    • Table 3–1 Controller Limitations for RAIDsets
  • Planning and Configuring Storagesets
  • Creating a Storageset and Device Profile
    • Figure 3–2 A Typical Storageset Profile
  • Determining Storage Requirements
  • Choosing a Storageset Type
    • Table 3–2 A Comparison of Different Kinds of Storagesets
    • Using Stripesets to Increase I/O Performance
      • Figure 3–3 Striping Lets Several Disk Drives Participate in Each I/O Request
      • Figure 3–4 Distribute Members across Ports
    • Using Mirrorsets to Ensure Availability
      • Figure 3–5 Mirrorsets Maintain Two Copies of the Same Data
      • Figure 3–6 First Mirrorset Members on Different Buses
    • Using RAIDsets to Increase Performance and Availability
      • Figure 3–7 Parity Ensures Availability; Striping Provides Good Performance
    • Using Striped Mirrorsets for Highest Performance and Availability
      • Figure 3–8 Striping and Mirroring in the Same Storageset
  • Cloning Data for Backup
    • Figure 3–9 CLONE Steps for Duplicating Unit Members
  • Backing Up Your Subsystem Configuration
    • Saving Subsystem Configuration Information to a Single Disk
    • Saving Subsystem Configuration Information to Multiple Disks
    • Saving Subsystem Configuration Information to a Storageset
  • Controller and Port Worldwide Names (Node IDs)
    • Restoring Worldwide Names (Node IDs)
    • Unit World Wide Names (LUN IDs)
  • Assigning Unit Numbers for Host Access to Storagesets
    • Figure 3–10 Controller Port ID and Unit Numbers in Transparent Failover Mode
    • Figure 3–11 Controller Port ID Numbers and Unit Numbers in Mulitple Bus Failover Mode
    • Assigning Unit Offsets
      • Figure 3–12 LUN Presentation Using Unit Offset on a Per-Host Basis
    • Assigning Access Paths
  • Creating a Storageset Map
    • Figure 3–13 Storageset Map
    • Device PTL Addressing Convention within the Controller
      • Figure 3–14 PTL Naming Convention
      • Figure 3–15 PTL Addressing in a Configuration
      • Figure 3–16 Locating Devices using PTLs
  • Planning Partitions
    • Figure 3–17 Partitioning a Single-Disk Unit
    • Defining a Partition
    • Guidelines for Partitioning Storagesets and Disk Drives
  • Choosing Switches for Storagesets and Devices
    • Enabling Switches
    • Changing Switches
  • RAIDset Switches
    • Replacement Policy
    • Reconstruction Policy
    • Membership
  • Mirrorset Switches
    • Replacement Policy
    • Copy Speed
    • Read Source
  • Device Switches
    • Transportability
    • Device Transfer Rate
  • Initialize Switches
    • Chunk Size
      • Figure 3–18 Chunk Size Larger than the Request Size
      • Figure 3–19 Chunk Size Smaller than the Request Size
      • Table 3–3 Maximum Chunk Sizes for a RAIDset
    • Save Configuration
    • Destroy/Nodestroy
  • Unit Switches
    • Table 3–4 Unit Switches
  • Configuring Storagesets with CLI Commands
    • Adding Disk Drives
    • Configuring a Stripeset
    • Configuring a Mirrorset
    • Configuring a RAIDset
    • Configuring a Striped Mirrorset
    • Configuring a Single-Disk Unit
    • Partitioning a Storageset or Disk Drive
    • Adding a Disk Drive to the Spareset
    • Removing a Disk Drive from the Spareset
    • Enabling Autospare
    • Deleting a Storageset
    • Changing Switches for a Storageset or Device
  • Configuring with the Command Console LUN
    • Enabling and Disabling the CCL
    • Finding the CCL Location
    • Multiple-Bus and Transparent Failover in SCSI-2 and SCSI-3 Modes
    • Adding Storage Units Using the CCL
  • Moving Storagesets
    • Figure 3–20 Moving a Storageset from one Subsystem to Another
• chapter 4
  • Troubleshooting
  • Maintenance Features
  • Troubleshooting Checklist
  • Troubleshooting Table
    • Table 4–1 Troubleshooting Table (Continued)
    • Figure 4–1 Troubleshooting: Host Cannot Access Unit
  • Significant Event Reporting
    • Events that cause controller termination
    • Events that do not cause controller operation to terminate
    • Fault Management Utility
    • Displaying Failure Entries
    • Translating Event Codes
      • Table 4–2 Event-Code Types
    • Controlling the Display of Significant Events and Failures
      • Table 4–3 FMU SET Commands (Continued)
  • Using VTDPY to Check for Communication Problems
    • Table 4–4 VTDPY Key Sequences and Commands
    • Checking Controller-to-Host Communications
      • Figure 4–2 Xfer Rate Region of the Default Display
    • Checking Controller-to-Device Communications
      • Figure 4–3 Regions on the Device Display
        • Table 4–5 Device Map Columns (Continued)
        • Table 4–6 Device Status Columns (Continued)
        • Table 4–7 Device-Port Status Columns
    • Checking Unit Status and I/O Activity
      • Figure 4–4 Unit Status on the Cache Display
        • Table 4–8 Unit Status Columns (Continued)
    • Checking Fibre Channel Link Errors
      • Figure 4–5 Fibre Channel Host Status Display
        • Table 4–9 Fibre Channel Host Status Display- Known Hosts (Connections)
        • Table 4–10 Fibre Channel Host Status Display- Port Status
        • Table 4–11 Fibre Channel Host Status Display- Link Error Counters (Continued)
        • Table 4–12 Tachyon First Digit
        • Table 4–13 Tachyon Second Digit
  • Checking for Disk-Drive Problems
    • Finding a Disk Drive in the Subsystem
    • Testing the Read Capability of a Disk Drive
      • Table 4–14 DILX Control Sequences
    • Testing the Read and Write Capabilities of a Disk Drive
      • Table 4–15 Data Patterns for Phase 1: Write Test
    • DILX Error Codes
      • Table 4–16 DILX Error Codes
  • Running the Controller’s Diagnostic Test
• chapter 5
  • Replacement Procedures
  • Replacing Modules in a Single Controller Configuration
    • Figure 5–1 Single Controller Configuration
    • Replacing the Controller and Cache Module in a Single Controller Configuration
    • Replacing the Controller in a Single Controller Configuration
    • Replacing the Cache Module in a Single Controller Configuration
  • Replacing Modules in a Dual-Redundant Controller Configuration
    • Figure 5–2 Dual-Redundant Controller Configuration
    • Replacing a Controller and Cache Module in a Dual-Redundant Controller Configuration
    • Replacing a Controller in a Dual-Redundant Controller Configuration
    • Replacing a Cache Module in a Dual-Redundant Controller Configuration
  • Replacing the External Cache Battery Storage Building Block
    • Figure 5–3 Single-Battery ECB SSB Configuration
    • Figure 5–4 Dual-battery ECB SBB Configuration
    • Replacing the External Cache Battery Storage Building Block With Cabinet Powered On
    • Replacing the External Cache Battery Storage Building Block With Cabinet Powered Off
  • Replacing a GLM
    • Figure 5–5 Location of GLMs in Controller
  • Replacing a PVA Module
    • Replacing the PVA in the Master Enclosure (ID 0)
    • Replacing the PVA in the First Expansion (ID 2) or Second Expansion (ID 3) Enclosure
  • Replacing an I/O Module
    • Figure 5–6 I/O Module Locations in a BA370 Enclosure
  • Replacing DIMMs
    • Figure 5–7 Cache-Module Memory Configurations
    • Table 5–1 Cache Module Memory Configurations
    • Removing DIMMs
    • Installing DIMMs
      • Figure 5–8 Installing a DIMM
  • Replacing a Fibre Cable or Hub
  • Replacing a PCMCIA Card
  • Replacing a Failed Storageset Member
    • Removing a Failed RAIDset or Mirrorset Member
    • Installing the New Member
  • Shutting Down the Subsystem
    • Disabling and Enabling the External Cache Batteries
      • Figure 5–9 Battery Disable Switch
  • Restarting the Subsystem
• chapter 6
  • Upgrading the Subsystem
  • Upgrading Controller Software
    • Installing a New Program Card
    • Downloading New Software
      • Figure 6–1 Location of Write-Protection Switch
    • Using CLCP to Install, Delete, and List Software Patches
  • Upgrading Firmware on a Device
    • Figure 6–2 Upgrading Device Firmware
    • HSUTIL Messages
      • Table 6–1 HSUTIL Messages and Inquiries (Continued)
  • Upgrading to a Dual-Redundant Controller Configuration
    • Installing a New Controller, Cache Module, and ECB
  • Upgrading Cache Memory
    • Table 6–2 Cache Module Memory Configurations
• appendix A
  • System Profiles
  • Device Profile
  • Storageset Profile
  • Enclosure Template
• appendix B
  • CLI Commands
  • CLI Overview
    • Using the CLI
    • Command Overview
    • Getting Help
    • Entering CLI Commands
      • Table B–1 Recall and Edit Command Keys
    • Changing the CLI Prompt
    • Command Syntax
• ADD CONNECTIONS
• ADD DISK
• ADD MIRRORSET
• ADD RAIDSET
• ADD SPARESET
• ADD STRIPESET
• ADD UNIT
  • Table B–2 ADD UNIT Switches for Storagesets
• CLEAR_ERRORS CLI
• CLEAR_ERRORS controller INVALID_CACHE
• CLEAR_ERRORS device-name UNKNOWN
• CLEAR_ERRORS unit-number LOST_DATA
• CLEAR_ERRORS unit-number UNWRITEABLE_DATA
• CONFIGURATION RESET
• CONFIGURATION RESTORE
• CONFIGURATION SAVE
• CREATE_PARTITION
• DELETE connections
• DELETE container-name
• DELETE FAILEDSET
• DELETE SPARESET
• DELETE unit-number
• DESTROY_PARTITION
• DIRECTORY
• HELP
• INITIALIZE
• LOCATE
• MIRROR
• POWEROFF
  • Table B–3 POWEROFF Switch Settings
• REDUCE
• RENAME
• RESTART controller
• RETRY_ERRORS UNWRITEABLE_DATA
• RUN
• SELFTEST controller
• SET connection-name
• SET controller
  • Table B–4 SET controller Switches
• SET device-name
• SET EMU
  • Table B–5 EMU Set Point Temperatures
• SET FAILEDSET
• SET FAILOVER
• SET mirrorset-name
• SET MULTIBUS_FAILOVER
• SET NOFAILOVER
• SET NOMULTIBUS_FAILOVER
• SET RAIDset-name
• SET unit-number
  • Table B–6 SET unit-number Switches for Existing Containers
• SHOW
• SHUTDOWN controller
• UNMIRROR
  • appendix C
    • LED Codes
    • Operator Control Panel LED Codes
      • Solid OCP Patterns
        • Table C–1 Solid OCP Patterns (Continued)
      • Flashing OCP Patterns
        • Table C–2 Flashing OCP Patterns (Continued)
  • appendix D
    • Event Reporting: Templates and Codes
    • Passthrough Device Reset Event Sense Data Response
      • Figure D–1 Pass-through Device Reset Event Sense Data Response Format
      • Last Failure Event Sense Data Response
        • Figure D–2 Template 01 - Last Failure Event Sense Data Response Format
      • Multiple-Bus Failover Event Sense Data Response
        • Figure D–3 Template 04 - Multiple-Bus Failover Event Sense Data Response Format
      • Failover Event Sense Data Response
        • Figure D–4 Template 05 - Failover Event Sense Data Response Format
      • Nonvolatile Parameter Memory Component Event Sense Data Response
        • Figure D–5 Template 11 - Nonvolatile Parameter Memory Component Event Sense Data Response Format
      • Backup Battery Failure Event Sense Data Response
        • Figure D–6 Template 12 - Backup Battery Failure Event Sense Data Response Format
      • Subsystem Built-In Self Test Failure Event Sense Data Response
        • Figure D–7 Template 13 - Subsystem Built-In Self Test Failure Event Sense Data Response Format
      • Memory System Failure Event Sense Data Response
        • Figure D–8 Template 14 - Memory System Failure Event Sense Data Response Format
      • Device Services Non-Transfer Error Event Sense Data Response
        • Figure D–9 Template 41 - Device Services Non-Transfer Error Event Sense Data Response Format
      • Disk Transfer Error Event Sense Data Response
        • Figure D–10 Template 51 - Disk Transfer Error Event Sense Data Response Format
    • Instance Codes
      • Instance Code Structure
        • Figure D–11 Structure of an Instance Code
      • Instance Codes and FMU
        • Figure D–12 Instance Code Format
        • Table D–1 Instance Codes (Continued)
    • Last Failure Codes
      • Last Failure Code Structure
        • Figure D–13 Structure of a Last Failure Code
      • Last Failure Codes and FMU
        • Figure D–14 Last Failure Code Format
        • Table D–2 Controller Restart Codes
        • Table D–3 Last Failure Codes (Continued)
    • Recommended Repair Action Codes
      • Table D–4 Recommended Repair Action Codes (Continued)
    • Component Identifier Codes
      • Table D–5 Component Identifier Codes (Continued)
    • Event Threshold Codes
      • Table D–6 Event Notification/Recovery Threshold Classifications
    • ASC/ASCQ Codes
      • Table D–7 ASC and ASCQ Codes (Continued)
  • appendix E
    • Controller Specifications
    • Physical and Electrical Specifications for the Controller
      • Table E–1 Controller Specifications
    • Environmental Specifications
      • Table E–2 StorageWorks Environmental Specifications
      • Glossary
      • Index