3.6.0 Matrix Server Installation Guide (5697-7079, February 2008)

Chapter 3: Install PolyServe Matrix Server 14

10. Configure FC Switches

NOTE: For all FC switches, it is best practice to place each HBA port and

its storage ports in a separate zone. No other initiator HBA port

should be present in this zone.

When certain problems occur on a server (for example, hardware

problems or the loss of matrix network communications), and the server

ceases to effectively coordinate and communicate with other servers in

the matrix, Matrix Server must remove the server’s access to filesystems

to preserve data integrity. This step is called fencing.

When you configure the matrix later in this procedure, you can select the

fencing method that you want to use:

• FibreChannel Switch-based fencing (also called “fabric fencing”).

When a server needs to be fenced, Matrix Server disables the server’s

access in the FibreChannel fabric.

• Web Management-Based Fencing via Server Reset/Shutdown (also

called “server-based fencing”). Matrix Server uses remote

management hardware on the server to remove its access to PSFS

filesystems.

For sites using fabric fencing, the FibreChannel switches must be

configured as described below to enable matrix operations across the

SAN.

NOTE: An issue discovered in PolyServe Matrix Server 3.6.0 prevents the

use of custom community strings with fabric-based fencing.

Clusters configured with fabric-based fencing must have both a

read/write community string named “private” and a read-only

community string named “public”. If this is not possible, the

fencing method must be changed to web-based fencing using iLO,

DRAC, IPMI, RSA, or another compatible management interface.

This regression will be fixed in a future release.

Configuring the FibreChannel switches is not required for sites using

server-based fencing. However, if the switches are configured as