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–18 HSG80 ACS Solution Software Version 8.6 for IBM AIX Installation and Configuration Guide
NOTE: The default condition is ENABLE_ACCESS_PATH=ALL. This specifies that access paths
to ALL hosts are enabled. It is recommended that the user restrict host access and that the
access path be carefully specified to avoid providing undesired host connections access to the
unit.
Restricting Host Access in Transparent Failover Mode
Three methods can be used to restrict host access to storage units in transparent failover
mode:
■ Using separate Fibre Channel links (either loop or fabric)
■ Enabling the access path of selected host connections on a shared loop or fabric
■ Setting offsets
NOTE: These techniques also work for a single controller.
Restricting Host Access by Separate Links
In transparent failover mode, host port 1 of controller A and host port 1 of controller B
share a common Fibre Channel link. Host port 2 of controller A and host port 2 of
controller B also share a common Fibre Channel link. If the host 1 link is separate from the
host 2 link, the simplest way to limit host access is to have one host or set of hosts on the
port 1 link, and another host or set of hosts on the port 2 link. Each host can then see only
units assigned to its respective controller port. This separation of host buses is shown in
Figure 1–11. This method applies only if the host 1 link and host 2 link are separate links.
NOTE: Compaq highly recommends that you provide access to only specific connections. This
way, if new connections are added, they will not have automatic access to all units. See the
following section Restricting Host Access by Disabling Access Paths.