3.5.1 Matrix Server Installation Guide (June 2008)

Chapter 2: Install Matrix Server and MxFS-Linux 17
12. Verify the SAN Configuration
This step verifies that the SAN devices are configured appropriately and
can be viewed from the servers that will be in the matrix. You will need to
perform this step on each server.
If an HBA driver has not already been loaded, run the following
command to load the driver:
# /etc/init.d/pmxs load
Next, run the following command to see a list of devices and review the
output to verify that the SAN is configured as you expect.
# cat /proc/partitions
For installations using fabric-based fencing, verify that Matrix Server can
communicate properly with each switch. Run the following command,
which displays the nameservice entries of connected and loaded HBA
and Storage ports.
# /opt/polyserve/sbin/PSANinfo –c <community string> <FC switch IP
address>
If the command fails, you will need to resolve the problem before
proceeding with the installation.
NOTE: Matrix Server and the FC switches must use the same community
string. You can set the community string for Matrix Server when
you configure the matrix later in this procedure.
13. Verify the Patched Kernel for MxFS-Linux
This step applies to SLES9 and RHEL4 sites that built the kernel from
source and will be using MxFS-Linux.
Verify that the MxFS-Linux patches have been correctly applied to the
kernel by running the command exportfssync -t. The command should
report the following:
# /opt/polyserve/sbin/exportfssync -t
Kernel supports NFS cluster-wide device aliases
If the command reports that the kernel does not support NFS cluster-
wide device aliases, either the MxFS-Linux patch has not been applied,
the kernel has not been compiled with the patches, or the recompiled
kernel has not been booted.