3.6.0 Matrix Server 3.6.0 Administration Guide (5697-7081, December 2007)

Chapter 3: Introduction to Matrix Server 9

The matrix includes these components:

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 (or a network switch and iSCSI arrays). Disks 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. It

includes kernel modules such as the PSFS filesystem, as well as several

processes and drivers.

Matrix Server also includes a Management Console that provides a

graphical interface for configuring the matrix and monitoring its

operation. The console can be run either remotely or from any server in

the matrix.

Following are some of the processes provided with Matrix Server:

ClusterPulse. 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). Provides a locking mechanism to

coordinate server access to shared resources in the matrix. All reads and