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
Installing and Configuring the HS-Series Agent 4–25
c. Option 23, CHECK LOCAL Node for Running Agent
This function is used to determine if there are any instances of the Agent process
running on the local node. It uses the ps
–eaf command and reports the results to
the operator.
d. Option 24, STOP Running Agent on LOCAL Node
This function is used to stop any instances of the Agent process running on the
local node. It may be invoked manually on each node in a cluster whose nodes may
have become isolated or have not yet rejoined the cluster.
e. Option 25, START the Agent on LOCAL Node
This function is used to start the Agent process running on the local node. It
automatically polls each node first as in Option 21 above, and it will not start the
Agent if one is running already on any node in the cluster.
Starting, Stopping and Checking for the Agent
The difference between a single-node configuration and an HACMP cluster is critical
when starting or stopping the Agent. To STOP a running agent, the script utility must
search the entire cluster and stop any Agent(s) found. This involves both stopping the
process with the
kill -9 command and the removing the entry from /ETC/INITTAB.
To START the Agent, the utility must first verify that no Agent is running already, and
then it must start the Agent on one node only. The /ETC/INITTAB service is not used in
the HACMP environment, because it would cause the Agent process to be re-spawned on
each restart of each node. This could easily lead to multiple Agents running on the same
HSG80 array, which is not allowed.
Password and Notification
The menu Options 1 and 2, involving Agent passwords and SNMP Enterprise OID's
respectively are the same in appearance as in the single node configuration. However, they
behave differently within the HACMP_Config.sh script because this information should
be kept consistent throughout the entire cluster. The HACMP_Config.sh script ensures
this consistency. Agent Notification Options 14 – 19 may be configured differently from
node-to-node within a cluster without interfering with the operation of HACMP or the
Agent.