3.1.2 Matrix Server Administration Guide

Chapter 2: Matrix Administration 22

• 64 service and/or device monitors per matrix (the total number of

service and device monitors cannot exceed 64)

• 10 event notifiers per matrix

• 4 network interface cards per server

• 4 FibreChannel ports per server

• 1024 unique paths to disks in the matrix

These limits will be increased as additional testing takes place.

Theoretically, the tested configuration limits can be exceeded up to the

bounds of the operating system. If you plan to configure your matrix

beyond the tested limits, please contact PolyServe Technical Support for

information about any known configuration issues or concerns.

Matrix Management Applications

Matrix Server provides two management applications: mxconsole, the

Management Console, and mx, the corresponding command-line

interface. These applications can be run from either a matrix server or a

local machine outside the matrix.

On a local machine, the management applications download their

rendering and application logic from the servers in the matrix. To

minimize startup time, the downloaded software is cached on the local

machine. The local machine then uses the software from the cache

whenever possible. If for some reason the software version running on

the server cannot be identified, the applications use the latest version in

their cache.

When you invoke mxconsole or mx from a local machine, by default the

application checks the current software version on the server to which it

is being connected and then downloads the software only if that version

is not already in the local cache.

Manage a Matrix with the Management Console

The Management Console can manipulate all entities in the matrix,

including entities that are currently down. For example, you can change

the configuration of a down server; it will learn its new configuration

when it comes back up and rejoins the matrix.