3.5.1 Matrix Server Upgrade Guide

Appendix B: Install the SLES9 Operating System and Kernel 57

to load its own HBA driver. (You may need to take steps to ensure that

the appropriate HBA driver is loaded. See your vendor documentation

for more information.)

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 correct HBA

driver is loaded. See the 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.)

5. Modify System Files

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

• /etc/hosts file. SuSE Linux places both localhost and the server name

on the 127.0.0.1 entry in the /etc/hosts file:

127.0.0.1 localhost servername

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

Normal operation of the matrix depends on a reliable network

hostname resolution service. If the hostname lookup facility becomes

unreliable, this can cause reliability problems for the running matrix.

Therefore, you should ensure that your hostname lookup services are

configured to provide highly reliable lookups, particularly for the

hostnames that are critical to matrix operation. These critical