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
5–24 HSG80 ACS Solution Software Version 8.6 for IBM AIX Installation and Configuration Guide
NOTE: The RUN CONFIG command does not delete disks from the controllers’ device table if a
disk has been physically removed or replaced. In this case, you must use the command:
DELETE DISKNNNN.
3. Verify the contents of the spareset by entering the following command:
SHOW SPARESET
Enabling Autospare
With AUTOSPARE enabled on the failedset, any new disk drive that is inserted into the
PTL location of a failed disk drive is automatically initialized and placed into the spareset.
If initialization fails, the disk drive remains in the failedset until you manually delete it
from the failedset.
To enable autospare, use the following command:
SET FAILEDSET AUTOSPARE
To disable autospare, use the following command:
SET FAILEDSET NOAUTOSPARE
During initialization, AUTOSPARE checks to see if the new disk drive contains metadata.
Metadata is information the controller writes on the disk drive when the disk drive is
configured into a storageset. Therefore, the presence of metadata indicates that the disk
drive belongs to, or has been used by, a storageset. If the disk drive contains metadata,
initialization stops. (A new disk drive will not contain metadata but a repaired or reused
disk drive might. To erase metadata from a disk drive, add it to the controller's list of
devices, then set it to be notransportable and initialize it.)
Deleting a Storageset
NOTE: If the storageset you are deleting is partitioned, you must delete each partitioned unit
before you can delete the storageset.
1. Show the storageset’s configuration:
SHOW STORAGESET-NAME
2. Delete the unit number that uses the storageset. Use the following command:
DELETE UNIT-NUMBER
3. Delete the storageset. Use the following command:
DELETE STORAGESET-NAME