3.1.2 Matrix Server Installation Guide

Table Of Contents

Chapter 2: Install PolyServe Matrix Server 14

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 in step 12.

10. Run the mxcheck Utility

This utility should be run on each server. It verifies that the server’s

configuration meets the requirements for running Matrix Server. Issue

the following command:

# /opt/polyserve/bin/mxcheck -l -p -t - install

The utility performs checks such as the following: operating system

version and configuration; available physical memory and disk space;

HBA driver versions; FibreChannel switch versions; network addresses.

The utility also attempts to access gateways and FC switches.

Output from the utility appears on the screen and is also written to the

/var/opt/polyserve/mxcheck directory. We recommend that you fix any

problems identified by mxcheck before you configure Matrix Server.

NOTE: If you have installed MxFS-Linux on a SLES9 system and mxcheck

fails with the error “Kernel does not support NFS cluster-wide

device aliases,” the booted kernel does not contain the MxFS-

Linux patches. See “Verify the Patched Kernel for MxFS-Linux” on

page 52 for information about correcting this problem.

11. Set Matrix Server Parameter for FalconStor

This step is needed only if a FalconStor device is included in your SAN

configuration.

The Matrix Server psd_round2_delay parameter must be set manually on

each server. This parameter is located in the scl.conf file, which by default

is located at /etc/opt/polyserve/scl.conf.

To set the psd_round2_delay parameter, locate the following lines in the

scl.conf file.