3.4.0 Matrix Server Administration Guide

Chapter 1: Introduction 3

Servers. Each server must be running Matrix Server.

Public LANs. A matrix can include up to four network interfaces per

server. Each network interface can be configured to support multiple

virtual hosts, which provide failover protection for Web, e-mail, file

transfer, and other TCP/IP-based applications.

Administrative Network. Matrix Server components communicate with

each other over a common LAN. The network used for this traffic is

called the administrative network. When you configure the matrix, you

can specify the networks that you prefer to use for the administrative

network traffic. For performance reasons, we recommend that these

networks be isolated from the networks used by external clients to access

the matrix.

Storage Area Network (SAN). The SAN includes FibreChannel switches

and RAID subsystems. Disks in a RAID subsystem are imported into the

matrix and managed from there. After a disk is imported, you can create

PSFS filesystems on it.

Software Components

The Matrix Server software is installed on each server in the matrix and

includes the following major components.

Management Console. Provides a graphical interface for configuring a

Matrix Server matrix and monitoring its operation. The console can be

run either remotely or from any server in the matrix.

ClusterPulse process. Monitors the matrix, controls failover of virtual

hosts and devices, handles communications with the Management

Console, and manages device monitors, service monitors, and event

notification.

Distributed Lock Manager (DLM) process. Provides a locking

mechanism to coordinate server access to shared resources in the matrix.

All reads and writes to a PSFS filesystem automatically obtain the

appropriate locks from the DLM, ensuring filesystem coherency.

SDMP process. Arbitrates and ensures that only one matrix has access to

shared SAN devices, in the event that a server loses connectivity.