HSG80 ACS Solution Software Version 8.7 for Compaq Tru64 UNIX Installation and Configuration Guide
Table Of Contents
- HSG80 ACS Solution Software Version 8.7 for Compaq Tru64 UNIX Installation and Configuration Guide
- About this Guide
- 1- Planning a Subsystem
- Defining Subsystems
- What is Failover Mode?
- Selecting a Cache Mode
- Enabling Mirrored Caching
- What is the Command Console LUN?
- Determining Connections
- Assigning Unit Numbers
- What is Selective Storage Presentation?
- 2- Planning Storage Configurations
- Where to Start
- Determining Storage Requirements
- Configuration Rules for the Controller
- Addressing Conventions for Device PTL
- Choosing a Container Type
- Creating a Storageset Profile
- Planning Considerations for Storageset
- Changing Characteristics through Switches
- Specifying Storageset and Partition Switches
- Specifying Initialization Switches
- Specifying Unit Switches
- Creating Storage Maps
- 3- Preparing the Host System
- Installing RAID Array Storage System
- Making a Physical Connection
- Preparing LUNs for Access by Tru64 UNIX FileSystem
- DECsafe Available Server Environment (ASE)
- HSG80 Units and Tru64 UNIX Utilities
- Solution Software Upgrade Procedures
- New Features, ACS 8.7 for Tru64
- 4- Installing and Configuring HSG Agent
- 5- FC Configuration Procedures
- Establishing a Local Connection
- Setting Up a Single Controller
- Setting Up a Controller Pair
- Configuring Devices
- Configuring Storage Containers
- Assigning Unit Numbers and Unit Qualifiers
- Configuration Options
- Verifying Storage Configuration from Host
- 6- Using CLI for Configuration
- 7- Backing Up, Cloning, and Moving Data
- 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
- B- Installing, Configuring, and Removing the Client
- C- SWCC Agent in TruCluster Environment
- SWCC Overview
- Running the SWCC Agent on a V4.0G Cluster
- Running the SWCC Agent under ASE Services
- Running the SWCC Agent on a V5.x Cluster
- Problems with Running the Agent on Multiple Clusters
- Configure the Controller
- Use Multiple-Bus Failover Mode
- Verify That the HSG80/HSG60 Unit Offsets Are Zero
- Install and Run the Agent on One Cluster Member
- Example of Installing the Agent on a Cluster Member
- Create the CAA Action Script
- Create the CAA Resource
- Glossary
- Index
SWCC Agent in TruCluster Environment
C–36 HSG80 ACS Solution Software Version 8.7 for Compaq Tru64 UNIX Installation and
Configuration Guide
Create the CAA Resource
Use the caa_profile command to create a CAA resource profile, and use the
caa_register command to register the resource after you have created it.
This procedure uses swcc as the resource name for the purpose of the example. Use
application as the resource type and specify the location of the action script.
If you want to start the resource automatically, regardless of whether it had been
stopped or running before the reboot, set auto_start to auto_start=1. Set auto_start=0 if
you want to start the resource only if it had been running before the reboot.
An example caa_profile -create command is as follows:
# caa_profile -create swcc -a swcc.scr -t application -o as=1
You can specify either a full pathname for the script file, or its filename, in which case
the caa_profile command looks for the file in the /var/cluster/caa/script directory.
By default, caa_profile -create enables steamd to run on all members with a placement
policy of balanced. The steamd daemon can therefore run on any member of the
cluster. If this default does not meet your needs, use the -c option to specify the
members that can host the application resource and use the -p option to specify a
placement policy.
The default check interval is 60 seconds. The check interval is the maximum amount
of time that an application can be unavailable to clients before CAA attempts to restart
it. Under some circumstances, this default can lead to a situation where a resource fails
and is not restarted quickly enough. You need to determine whether the 60-second
check interval is suitable.