3.1.2 Matrix Server Installation Guide
Table Of Contents
- Contents
- Configuration Information
- Install PolyServe Matrix Server
- Supported Operating Systems
- Contents of the Matrix Server Distribution
- Installation Procedure
- Installation Checklist
- 1. Set Up the SAN Environment
- 2. Install a Supported Operating System and Kernel
- 3. Install Third-Party MPIO Software (Optional)
- 4. Verify Downloaded RPMs
- 5. Install PolyServe Matrix Server
- 6. Install the Quota Tools RPM (Optional)
- 7. Specify an HBA Driver If Necessary
- 8. Reboot and Verify the HBA Configuration
- 9. Verify the SAN Configuration
- 10. Run the mxcheck Utility
- 11. Set Matrix Server Parameter for FalconStor
- 12. Configure the Matrix from the Management Console
- Test the Fencing Configuration
- Install the Management Console on Other Hosts
- Administer init.d Scripts
- Uninstall PolyServe Matrix Server
- Uninstall the Management Console
- Install MxFS-Linux
- Install the RHEL4 Operating System and Kernel
- Install the SLES9 Operating System and Kernel
- Configure the Matrix from the Command Line
- Run mxconfig
- Matrix Server License File
- Specify the Matrix Password
- Specify the Network Authentication Secret Password
- Select the Cluster Administrative Traffic Protocol
- Select a Fencing Method
- Configure FibreChannel Switches
- Set the SNMP Community String
- Modify Disk Partitioning for Membership Partitions
- Create Membership Partitions
- Add a Snapshot Configuration
- Currently, hardware snapshots are supported only on Hewlett-Packard StorageWorks Enterprise Virtual Array (EVA) storage arrays. ...
- Export the Configuration
- Verify the Fencing Configuration
- Complete the Installation
- Run mxconfig

Chapter 1: Configuration Information 4
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
• The network topology should be symmetrical; each server in the
matrix should be connected to the same set of networks.
• The following flags must be set on each network interface: Broadcast,
Multicast, Up, Running.
Matrix SAN Configuration Guidelines
Following are guidelines for configuring the matrix SAN to be used with
Matrix Server:
• For all FC switches, it is best practice to place each HBA port and its
storage ports in a separate zone. No other initiator HBA port should
be present in this zone.
• The FC switches managed by the matrix must be from the same
vendor. Switches that will not be managed by Matrix Server can be
from other vendors only if all of the vendors have approved the
configuration.
• With fabric fencing, if the servers are connected to switches in
multiple fabrics, the physical ports on each switch must be assigned to
unique domain IDs. A different domain ID must be used on each
fabric (any given domain ID can exist on only one fabric in the SAN).
For example, if a server is connected to two switches that are not in the
same fabric, switch1 could use domain ID 6 and switch2 could use
domain ID 7. Domain ID 6 must not exist on the fabric containing
switch2 and domain ID 7 must not exist on the fabric containing
switch1.
• To eliminate single points of failure, configure the SAN to use
multipath I/O. See the PolyServe Matrix Server Administration Guide for
some sample matrix configurations that include this feature.
• Disk Power Management must be disabled on any Windows systems
that have access to the SAN storage.
NOTE: You can attach a matrix server to other SANs that are not under
Matrix Server control. These SANs can include tape drives and
non-PSFS filesystems. You can use Linux utilities or other
applications to access these devices and filesystems.