3.5.1 Matrix Server Administration Guide

Chapter 18: SAN Maintenance 303

vendor-supplied libhbaapi. (Check with your vendors to determine

whether OLI is supported.)

When this lower-level OLI support is in place, inserting a new disk will

cause a new device to automatically become eligible for importing. The

disk can be imported with the Management Console or mx utility, and

can be used normally from that point forward.

If OLI is not possible with your hardware combination, you will need to

restart Matrix Server after inserting a new disk. The disk will then be

visible to the matrix.

Changing the Number of LUNs Can Cause Matrix

Failure

Matrix Server uses worldwide names and LUN numbers to associate PSD

device names with SAN devices. If the LUN numbers are changed on an

array (for example, by combining LUNs or breaking a LUN into multiple

LUNs), the matrix can fail to start when servers are rebooted because the

PSD device names are no longer associated with the correct LUNs. Matrix

Server cannot automatically detect a change in LUN numbering because

its identification mechanism uses the worldwide name, which changes as

the LUN changes.

To minimize downtime, if you need to make changes to your storage

which will result in the LUN numbers on the array changing, contact

PolyServe Technical Support before making the change.

However, if this situation should occur, you can use the mxmpconf utility

to restore the membership partitions. You will then be able to restart the

matrix. For assistance in restoring access to PSFS filesystems, contact

PolyServe Technical Support.

NOTE: LUNs can safely be resized. Problems occur only if LUN

numbering on the array is changed.