3.6.0 Matrix Server Upgrade Guide (5697-7085, February 2008)

Chapter 2: Overview 5

upgrade. (The stand-alone PolyServe Management Console provided

with the 3.6 release is backward-compatible and can access nodes

running Matrix Server 3.2 or 3.4.)

• Matrix Server now uses single sign-on authentication. The admin user,

the mxpasswd file, and the mxpasswd command are now obsolete.

• The minimum size for a membership partition is now 1GB. If your

existing membership partitions are too small to accommodate the new

mxds datastore, which is included in the membership partitions, an

alert will be generated after the upgrade to 3.6. Chapter 5 describes

how to replace the existing membership partitions.

Custom Community Strings Not Supported with

Fabric-Based Fencing

An issue discovered in PolyServe Matrix Server 3.6.0 prevents the use of

custom community strings with fabric-based fencing. For upgrades to

3.6.0, 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.

MxDB for SQL Server Requirements and Changes

Before upgrading MxDB for SQL Server, ensure that the following

requirements are met:

• A DNS entry must exist for each Virtual SQL Server/IP address. The

entry must include an A record and a PTR record for forward and

reverse lookup. Windows authentication may fail if these records do

not exist.

You should be aware of the following changes:

• The architecture of MxDB for SQL Server has changed significantly in

the 3.6.0 release. To enable existing MxDB for SQL Server

configurations to be upgraded, the MxUpgrade_SQL-3.6.0 upgrade

preparation tool must be run before the node is upgraded to 3.6.0. See