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–5
Failover Mode
Failover is a way to keep the storage array available to the host if one of the controllers
becomes unresponsive. A controller can become unresponsive because of a hardware
failure, such as a controller. Failover keeps the storage array available to the hosts by
allowing the surviving controller to take over total control of the subsystem.
There are two failover modes:
■ Transparent, which is handled by the surviving controller and is invisible
(transparent) to the hosts.
■ Multiple-bus, which is handled by the hosts.
Transparent Failover Mode
Transparent failover mode has the following characteristics:
■ Hosts do not know failover has taken place
■ Units are divided between host ports 1 and 2
A unit or storage unit is a physical or virtual device of the subsystem. It is typically
assigned a logical unit number (LUN) and is managed by the HSG80 controller and
presented to a server through the Fibre Channel bus and the server’s host bus adapter.
Disks that are set up as independent disks (JBODs) or RAIDsets are referred to as
storagesets. Storagesets are units.
In transparent failover mode, host port 1 of controller A and host port 1 of controller B
must be on the same Fibre Channel link. Host port 2 of controller A and host port 2 of
controller B must also be on the same Fibre Channel link. Depending on operating system
restrictions and requirements, the port 1 link and the port 2 link can be separate links, or
they can be the same link.
At any time, host port 1 is active on only one controller, and host port 2 is active on only
one controller. The other ports are in standby mode. In normal operation, both host port 1
on controller A and host port 2 on controller B are active. A representative configuration is
shown in Figure 1–5. The active and standby ports share port identity, enabling the
standby port to take over for the active one. If one controller fails, its companion controller
(known as the surviving controller) takes control by making both its host ports active, as
shown in Figure 1–6.
Units are divided between the host ports: