HSG80 ACS Solution Software V8.6 for IBM AIM Installation and Configuration Guide
Table Of Contents
- HSG80 ACS Solution Software Version 8.6 for IBM AIX
- Contents
- Figures
- Tables
- About this Guide
- Chapter 1
- Planning a Subsystem
- Chapter 2
- Planning Storage
- Where to Start
- Configuration Rules
- Device PTL Addressing Convention
- Determining Storage Requirements
- Choosing a Container Type
- Creating a Storageset Profile
- Storageset Planning Considerations
- Storageset Expansion Considerations
- Partition Planning Considerations
- Changing Characteristics through Switches
- Storageset and Partition Switches
- Initialization Switches
- Unit Switches
- Storage Maps
- Chapter 3
- Preparing the Host System
- Chapter 4
- Installing and Configuring the HS-Series Agent
- Why Use StorageWorks Command Console (SWCC)?
- Installation and Configuration Overview
- About the Network Connection for the Agent
- Before Installing the Agent
- Installing and Configuring the Agent
- Running the Agent
- Reconfiguring the Agent
- Uninstall Agent, Storageworks Software, and Cambex Driver.
- High Availability Cluster Multi-Processor (HACMP)
- Enabler Software
- General Note on Software Installation
- SWCC Clients
- Running the Agent
- HACMP Implementation for the Agent
- Prerequisites
- Implementation
- Installing the Agent on an HACMP Cluster
- Installing and Configuring the Client on an HACMP cluster
- Operation of the Agent on an HACMP Cluster
- Normal Operation of the Agent on an HACMP Cluster
- Starting, Stopping and Checking for the Agent
- Password and Notification
- Client Functions and Storage Subsystem Options
- Failover with Agent as Part of a Resource Group
- Client IP Address
- Event Scripts
- Notification within HACMP
- Node Isolation Recovery
- Failure of the Agent
- Polling all nodes in cluster for presence of a running Agent
- Restarting the Agent on surviving node
- Notification
- Supporting Tools
- HACMP for AIX Primary Event Scripts
- HACMP for AIX Secondary Event Scripts
- Chapter 5
- Configuration Procedures
- Establishing a Local Connection
- Setting Up a Single Controller
- Setting Up a Controller Pair
- Configuring Devices
- Configuring a Stripeset
- Configuring a Mirrorset
- Configuring a RAIDset
- Configuring a Striped Mirrorset
- Configuring a Single-Disk Unit (JBOD)
- Configuring a Partition
- Assigning Unit Numbers and Unit Qualifiers
- Configuration Options
- Chapter 6
- Verifying Storage Configuration from the Host
- Chapter 7
- Configuration Example Using CLI
- Chapter 8
- Backing Up the Subsystem, Cloning Data for Backup, and Moving Storagesets
- Appendix A
- Subsystem Profile Templates
- Storageset Profile
- Storage Map Template 1 for the BA370 Enclosure
- Storage Map Template 2 for the second BA370 Enclosure
- Storage Map Template 3 for the third BA370 Enclosure
- Storage Map Template 4 for the Model 4214R Disk Enclosure
- Storage Map Template 5 for the Model 4254 Disk Enclosure
- Storage Map Template 6 for the Model 4310R Disk Enclosure
- Storage Map Template 7 for the Model 4350R Disk Enclosure
- Storage Map Template 8 for the Model 4314R Disk Enclosure
- Storage Map Template 9 for the Model 4354R Disk Enclosure
- Appendix B
- Installing, Configuring, and Removing the Client
- Appendix C
- Exploitation of the CLONE and SNAPSHOT Functions of the HSG80 in an AIX Environment
- Glossary
- Index
Figures
Figure 1 General configuration flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Figure 2 Configuring storage with the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Figure 3 Configuring storage with SWCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Figure 1–1 Location of controllers and cache modules in a Model 2200 enclosure . . . . . . . . . . . 1–2
Figure 1–2 Location of controllers and cache modules in a BA370 enclosure . . . . . . . . . . . . . . . 1–3
Figure 1–3 “This controller” and “other controller” for the Model 2200 enclosure . . . . . . . . . . . 1–4
Figure 1–4 “This controller” and “other controller” for the BA370 enclosure . . . . . . . . . . . . . . . 1–4
Figure 1–5 Transparent failover
—normal operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
Figure 1–6 Transparent failover
—after failover from controller B to controller A . . . . . . . . . . . 1–7
Figure 1–7 Mirrored caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–9
Figure 1–8 Connections in separate-link, transparent failover mode configurations . . . . . . . . . 1–12
Figure 1–9 Connections in single-link, transparent failover mode configurations . . . . . . . . . . . 1–13
Figure 1–10 LUN presentation to hosts, as determined by offset . . . . . . . . . . . . . . . . . . . . . . . . 1–15
Figure 1–11 Limiting host access in transparent failover mode . . . . . . . . . . . . . . . . . . . . . . . . . 1–19
Figure 1–12 Placement of the worldwide name label on the Model 2200 enclosure . . . . . . . . . 1–22
Figure 1–13 Placement of the worldwide name label on the BA370 enclosure . . . . . . . . . . . . . 1–22
Figure 2–1 PTL naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Figure 2–2 PTL addressing in a configuration in a BA370 enclosure. . . . . . . . . . . . . . . . . . . . . . 2–4
Figure 2–3 PTL addressing in a single-bus configuration, six Model 4310R disk enclosures . . . 2–6
Figure 2–4 PTL addressing in a dual-bus configuration, three Model 4350R disk enclosures. . . 2–7
Figure 2–5 PTL addressing in a single-bus configuration, six Model 4314R disk enclosures . . . 2–8
Figure 2–6 PTL addressing in a dual-bus configuration, three Model 4354R disk enclosures. . . 2–9
Figure 2–7 Mapping a unit to physical disk drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–10
Figure 2–8 Container types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–11
Figure 2–9 An example storageset profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
Figure 2–10 A 3-member RAID 0 stripeset (example 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–14
Figure 2–11 A 3-member RAID 0 stripeset (example 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–15
Figure 2–12 Mirrorsets maintain two copies of the same data . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17
Figure 2–13 Mirrorset example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–17