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 3100
# for each of the device group secondary volumes.
# The remote Raid Manager instances are required to get status or provide
# control of the remote devices in the device group. All remote hosts
# must be defined here, so that the failure of one remote host will prevent
# obtaining status.
#
# <dev_group>
# This is the same device group names as defined in dev_group of HORC_DEV.
# <ip_address>
# This parameter is used to define the network address of the remote hosts
# with Raid Manager access to the device group. This can be either an
# IP address or a host name.
# <service>
# This parameter is used to specify the port name assigned to the Raid
# Manager instance, which must be registered in /etc/services. If this is
# a port number rather than a port name, then the port number will be used.
HORCM_INST
#dev_group ip_address service
pkgA ftsys1a horcm0
pkgA ftsys2a horcm0
pkgB ftsys1a horcm0
pkgB ftsys2a horcm0
pkgC ftsys1a horcm0
pkgC ftsys2a horcm0
pkgD ftsys1a horcm0
pkgD ftsys2a horcm0
Configuring Automatic Raid Manager Startup
After editing the Raid Manager configuration files and installing them
on the nodes that are attached to the XP Series disk arrays, you should
configure automatic Raid Manager startup on the same nodes. You do
this by editing the rc script /etc/rc.config.d/raidmgr. Set the
START_RAIDMGR parameter to 1, and define RAIDMGR_INSTANCE as the
number of the Raid Manager instance you are using with MetroCluster.
By default, this is zero (0).
An example of the edited startup file is shown below:
#*************************** RAIDMANAGER
*************************
# MetroCluster with Continuous Access Toolkit script for
configuring the