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

1–20 HSG80 ACS Solution Software Version 8.6 for IBM AIX Installation and Configuration Guide
For example:
In Figure 1–11, restricting the access of unit D101 to host 3, the host named BROWN can
be done by enabling only the connection to host 3. Enter the following commands:
SET D101 DISABLE_ACCESS_PATH=ALL
SET D101 ENABLE_ACCESS_PATH=BROWN1B2
If the storage subsystem has more than one host connection, carefully specify the access
path to avoid providing undesired host connections access to the unit. The default
condition for a unit is that access paths to all host connections are enabled. To restrict host
access to a set of host connections, specify DISABLE_ACCESS_PATH=ALL for the unit,
then specify the set of host connections that are to have access to the unit.
Enabling the access path to a particular host connection does not override previously
enabled access paths. All access paths previously enabled are still valid; the new host
connection is simply added to the list of connections that can access the unit.
IMPORTANT: The procedure of restricting access by enabling all access paths then disabling
selected paths is not recommended because of the potential data/security breach that occurs
when a new host connection is added.
Restricting Host Access by Offsets
Offsets establish the start of the range of units that a host connection can access.
For example:
In Figure 1–11, assume both host connections on port 2 (connections BLACK1B2 and
BROWN1B2) initially have the default port 2 offset of 100. Setting the offset of
connection BROWN1B2 to 120 will present unit D120 to host BROWN as LUN 0.
SET BROWN1B2 UNIT_OFFSET=120
Host BROWN cannot see units lower than its offset, so it cannot access units D100 and
D101. However, host BLACK can still access D120 as LUN 20 if the operating system
permits. To restrict access of D120 to only host BROWN, enable only host BROWN’s
access, as follows:
SET D120 DISABLE_ACCESS_PATH=ALL
SET D120 ENABLE_ACCESS_PATH=
BROWN1B2