Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Metropolitan Cluster Using MetroCluster/CA
Preparing an MC/ServiceGuard Cluster for MetroCluster /CA
Chapter 394
Creating the Raid Manager Configuration
The Raid Manager configuration file must be edited and customized on
each node that is attached to one of the XP Series disk arrays. The file is
named using the following convention:
horcm<instance number>.conf
All MetroCluster packages must use the same Raid Manager instance,
and must be configured in the same configuration file. In the examples in
this chapter, instance zero is assumed, which is configured in file
horcm0.conf.
Here are the steps to follow for creating the configuration:
1. Copy the default Raid Manager configuration file to an
instance-specific name:
# cp /etc/horcm.conf /etc/horcm0.conf
2. Create a minimum Raid Manager configuration file by editing the
following sections of the file created in the previous step:
HORCM_MON Enter the host-name of the system on which you
are editing and the TCP/IP port number specified
for this Raid Manager instance in the /etc/services
file.
HORCM_CMD Enter the primary and alternate link device file
names for both primary and redundant command
devices (for a total of four raw device file names).
WARNING Make sure that the redundant command device is not on the
same physical device as the primary command device. Also,
make sure that the two command devices are on different
buses inside the XP Series disk array.
3. If the Raid Manager protection facility is enabled, export the
HORCPERM environment variable to the HORCM permission file:
# export HORCMPERM=/etc/horcmperm0.conf
If the Raid Manager protection facility is not used or disabled, export
the HORCPERM environment variable as follows:
# export HORCMPERM=MGRNOINST