Installation guide

Section 3.1:Steps for Installing and Initializing the Cluster Software 57
3.1.1 Editing the rawdevices File
The /etc/sysconfig/rawdevices file is used to map the raw devices for the quorum parti-
tions each time a cluster system boots. As part of the cluster software installation procedure, edit the
rawdevices file on each cluster system and specify the raw character devices and block devices for
the primary and backup quorum partitions. This must be done prior to running the cluconfig utility.
If raw devices are employed in a cluster service, the rawdevices file is also used to bind the devices
at boot time. Edit the file and specify the raw character devices and block devices that you want to bind
each time the system boots. To make the changes to the rawdevices file take effect without requiring
a reboot, perform the following command:
service rawdevices restart
The following is an example rawdevices file that designates two quorum partitions:
# raw device bindings
# format: <rawdev> <major> <minor>
# <rawdev> <blockdev>
# example: /dev/raw/raw1 /dev/sda1
# /dev/raw/raw2 8 5
/dev/raw/raw1 /dev/sdb1
/dev/raw/raw2 /dev/sdb2
See Configuring Quorum Partitions in Section 2.4.4 for more information about setting up the quorum
partitions. See Creating Raw Devices in Section 2.4.4 for more information on using the raw command
to bind raw character devices to block devices.
Note
The rawdevices configuration must be performed on both cluster members.
3.1.2 Configuring the Cluster Alias
A cluster alias is a means of binding an IP address to one of the active cluster members. At any point
in time this IP address will only be bound by one of the cluster members. This IP address is a useful
conveniencefor system management and monitoring purposes. For example, suppose an administrator
wishes to be able to telnet into an active cluster member, but does not care which cluster member.
In this case, simply telnet to the cluster alias IP address (or associated name). The principal usage
of the cluster alias is to enable the direction of the cluster GUI monitoring interface to connect to an
active cluster member. In this manner, if either of the cluster members are not currently active it is
still possible to derive cluster status while being abstracted from having to designate a specific cluster
member to connect to.