HP StorageWorks HSG80 ACS Solution Software V8.8 for Tru64 UNIX Installation and Configuration Guide (AA-RV1VA-TE, March 2005)

SWCC Agent in TruCluster Environment
267HSG80 ACS Solution Software V8.8 for Tru64 UNIX Installation and Configuration Guide
Note: The recommended edit to the /sbin/init.d/swcc file prevents the
/usr/opt/SWCCx/scripts/swcc_config utility from starting, stopping, or
restarting SWCC when the swcc resource is registered with CAA. However, swcc_config
is not aware of this change, and still attempts to start, stop, and restart SWCC if you
choose these options. This action results in a problem-status message.
If you did not modify the /sbin/init.d/swcc script as described in Edit the
Startup Script, do not use these options because they can interfere with CAA
control of the swcc resource. For example, if you use
/usr/opt/SWCCx/scripts/swcc_config to stop SWCC on a cluster
member, CAA then restarts the swcc resource on that member or another member.
Verifying Success
After you apply the procedure for using swcc in a cluster, you can verify whether
it was successful by performing the following steps. You will probably find it
easier to call the CAA commands interactively to test your work and get
immediate feedback.
In this discussion, the active member is the member on which CAA starts the
resource; it may or may not be the member that you are currently using.
To determine whether the CAA resource is online, and, if so, on which member,
use the caa_stat command.
If the resource is not online, use the caa_start command to start the CAA resource.
CAA reports the member on which the resource is started, as follows:
# caa_start swcc
Attempting to start `swcc` on member
`deli` Start of `swcc` on member `deli` succeeded.
To verify that swcc is running on the member, use the ps command to determine
whether the steamd daemon is running on the member:
# ps agx | grep steamd
540567 pts/1 S 0:00.11 /usr/opt/SWCC5xx/bin/steamd sF
540850 pts/1 S + 0:00.00 grep steamd
To verify that the swcc agent is accessible from the client, use the client running
on a PC to display information about the storage configuration. Make sure to use
the cluster alias when connecting from the client.
To stop the CAA resource, use the caa_stop swcc command on any member.