3.5.1 Matrix Server Administration Guide

Chapter 1: Introduction 6

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. It

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

daemons 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 daemons 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

writes to a PSFS filesystem automatically obtain the appropriate locks

from the DLM, ensuring filesystem coherency.

grpcommd. Manages Matrix Server group communications across the

matrix.

mxeventd. The distributed event subscription and notification service.

mxinit. Starts or stops Matrix Server and monitors Matrix Server

processes.

mxlogd. Manages global error and event messages. The messages are

written to the /var/log/polyserve/matrix.log file on each server.

mxregd. Manages portions of the internal Matrix Server configuration.