3.5.1 Matrix Server Upgrade Guide

Appendix A: Install the RHEL4 Operating System 47

SAN Boot Disk

With certain storage arrays, the boot disk can be on the SAN. In this case,

the HBA driver must be loaded with the kernel so that the boot disk can

be located. (You may need to take steps to ensure that the appropriate

HBA driver is loaded. See your vendor documentation for more

information.) You will need to use non-fabric fencing with this

configuration.

Install Other HBA Drivers

If your configuration requires either an HBA driver version that is

provided with Matrix Server but is not the default, or an HBA driver

version that is not provided with Matrix Server, you can install that

version after Matrix Server is installed on the server. (The installation

procedure in Chapter 2 specifies when to install the driver.)

3. Modify System Files

You may need to modify the following files on each server:

• /etc/hosts file. Red Hat Linux places both localhost and the server

name on the 127.0.0.1 entry in the /etc/hosts file. For example:

127.0.0.1 localhost.localdomain localhost

Matrix Server requires that the server name appear on a separate line

with its real IP address, as in the following example. Be sure to move

the server name to its own line in the /etc/hosts file on each server. We

recommend that you specify the fully qualified name.

127.0.0.1 localhost

10.1.1.100 servername.localdomain

• /etc/updatedb.conf file. We recommend that you add psfs to the

PRUNE_FS list contained in this file. Following is an example:

PRUNEFS="sysfs selinuxfs usbdevfs devpts NFS nfs afs sfs

proc smbfs cifs autofs auto iso9660 udf psfs"

• /etc/init.d/halt script. When a server is rebooted, the default /etc/init.d/

halt script may need to probe each disk partition to locate the root

filesystem. If a server has been excluded from the matrix, these probes

can generate SCSI disk errors or hangs when the server is rebooted.