3.4.0 Matrix Server Installation Guide

Chapter 2: Install PolyServe Matrix Server 13

• For McDATA switches, each server should be placed in a separate

zone with its storage. Also, domain-wide RSCNs should be disabled.

• For Cisco switches, each server should be placed in a separate zone

with its storage.

• If the servers are connected to switches in multiple fabrics, the

physical ports on each switch must be assigned to unique domain IDs.

A different domain ID must be used on each fabric (any given domain

ID can exist on only one fabric in the SAN). For example, if a server is

connected to two switches that are not in the same fabric, switch1

could use domain ID 6 and switch2 could use domain ID 7. Domain

ID 6 must not exist on the fabric containing switch2 and domain ID 7

must not exist on the fabric containing switch1.

Typically these tasks can be performed from the FC switch or from third-

party applications. Refer to your FC switch or application documentation

for more information.

11. Create LUNs for the Membership Partitions and

Modify Partition Tables

Matrix Server uses a set of membership partitions to control access to the

SAN. The membership partitions are also used to store the device naming

database, which includes the global device names that Matrix Server

assigns to the SAN disks placed under its control.

Matrix Server can use either one or three membership partitions. To

ensure that a membership partition is always available, we strongly

recommend that you use three membership partitions.

If your disk array software provides the capability to create LUNs, we

recommend that you create three LUNs for the membership partitions.

Each LUN should be a minimum of 100 MB in size.

After creating the LUNs, use the Windows Logical Disk Management

(WLDM) utility to create a single partition on each LUN.