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
Exploitation of the CLONE and SNAPSHOT Functions of the HSG80 in an AIX Environment C–5
3. If the copy is to be a SNAPSHOT, skip to Step 5. Otherwise follow the CLONE
procedure described in Chapter 8. Repeat the procedure for each target drive. As
mentioned previously, the hdisks associated with the storage system drives and
targeted for CLONE copy can remain available and logical volumes mounted and
accessible in AIX. When the CLONE is complete, go to Step 6.
4. For SNAPSHOT, the HSG80 controller must be loaded with “S” type firmware before
this function can be invoked. Using a terminal attached to the HSG80 controller serial
interface, select and initialize disk devices in the storage system having the same
capacity as the target unit drives determined in Step 3. Create a one-disk mirror
container for each selected drive. Add the drives as SNAPSHOT units using the
following CLI command construct:
ADD SNAPSHOT <New Unit Number> <Mirror Container Name> <Target Disk Unit>
5. Ensure connection access to the new drive. For SNAPSHOT, connection access to the
new disk unit is disabled and must be enabled; for CLONE, the new disk unit
connection access is set to ALL. Depending on the storage system configuration with
the host or hosts, it may be necessary to tailor host access to the new drive in the
storage unit. Refer to the section, Restricting Host Access, in Chapter 1 for setting
drive/host access. For new SNAPSHOT drives, if there are no host access restrictions
then issue the following command for each new drive:
SET <New Drive Unit> ENABLE_ACCESS=ALL
Once the access connection has been appropriately set, the new drive should be
available for AIX use.
6. Run cfgmgr on the AIX system after which a new set of hdisks equal to the number of
target hdisks should become available.
7. The new hdisks can be verified as copies of the originals by examining the respective
hdisk physical volume IDs (PVID). To do this, issue the lspv AIX command which is
shown in the following example:
# lspv
hdisk0 000518660c11216frootvg
hdisk1 003b5075af8b1c4edatavg
hdisk2 003b50756c0fc93edatavg
hdisk3 003b5075af8b1c4edatavg
hdisk4 003b50756c0fc93edatavg
hdisk3 and hdisk4 are the copied drives created by the storage system disk copy
procedure (CLONE or SNAPSHOT) that also became available after invoking AIX
cfgmgr. The PVID of both drives match those respectively in hdisk1 and hdisk2.