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

Planning a Subsystem 1–15
If no value is specified for offset, then connections on port 1 have a default offset of 0 and
connections on port 2 have a default offset of 100.
For example, if all host connections use the default offset values, unit D2 will be presented
to a port 1 host connection as LUN 2 (unit number of 2 minus offset of 0). Unit D102 will
be presented to a port 2 host connection as LUN 2 (unit number of D102 minus offset of
100).
Figure 1–10 shows how units are presented as different LUNs, depending on the offset of
the host. In this illustration, host connection 1 and host connection 2 would need to be on
host port 1; host connection 3 would need to be on host port 2.
Figure 1–10. LUN presentation to hosts, as determined by offset
Offsets other than the default values can be specified. For example, unit D17 would be
visible to a host connection on port 1 that had an offset of 10 as LUN 7 (unit number of 17
minus offset of 10). The unit would not be visible to a host connection with a unit offset of
18 or greater, because that offset is not within the unit’s range (unit number of 17 minus
offset of 18 is a negative number).
Similarly, unit D127 would be visible to a host connection on port 2 that had an offset of
120 as LUN 7 (unit number of 127 minus offset of 120). The unit would not be visible to a
host connection with a unit offset of 128 or greater, because that offset is not within the
unit’s range (unit number of 127 minus offset of 128 is a negative number).
Controller
units
Host
connection 1
Offset: 0
Host
connection 2
Offset: 20
Host
connection 3
Offset: 100
LUN 0
LUN 1
LUN 2
LUN 3
LUN 20
LUN 21
LUN 0
LUN 1
LUN 0
LUN 1
LUN 2
LUN 30
LUN 31
D0
D1
D2
D3
D20
D21
D100
D101
D102
D130
D131
CXO6455B