3.5.1 Matrix Server Administration Guide

Chapter 2: Matrix Administration 19

adversely affect the entire matrix. If you need to add or delete a

network interface on a particular server, first stop Matrix Server on

that server. Then make your administrative change and restart Matrix

Server.

• A network interface should not be modified or taken down while

Matrix Server is running. Attempting to do this can cause adverse

effects. If any part of a network interface definition needs to be

changed, stop Matrix Server on the affected server, shut down the

network, and then make the change. When the change is complete,

bring up the network and restart Matrix Server.

Servers

• For best performance, we recommend that you monitor the matrix

from a separate administrative station rather than from a server in the

matrix. The Management Console can be installed on Linux or

Windows systems.

• Matrix Server components can fail if the /var filesystem fills up. To

avoid this situation, move /var/opt/polyserve to a separate partition

containing at least 400 MB of free space.

• To ensure that file times are consistent across the matrix, it is

important that all matrix servers operate with synchronized time-of-

day clocks. An NTP server is one commonly used mechanism for

synchronizing system clocks.

SAN

• When fabric fencing is configured, do not enable or disable the

FibreChannel ports used by the matrix. Matrix Server must have

complete control over these ports to protect the integrity of the shared

filesystems on the SAN. Matrix Server will reenable a port if it detects

that the port has been disabled manually.

• When fabric fencing is configured, do not change the physical

connection between a server and a FibreChannel switch while Matrix

Server is running on that server. Doing so may result in filesystem

corruption. For example, the connection must not be moved from one

switch port to another, and a new FibreChannel connection for the