3.1.2 Matrix Server SLES9 Release Notes

PolyServe Matrix Server Release Notes 3

• Defect 12507. After a server was fenced, an alert stating that the server

should be rebooted did not always appear on the PolyServe

Management Console.

• Defect 12522. A method was needed to notify Matrix Server that a

node is down and does not need to be fenced.

• Defect 12528. UIDs used for the MSA 1500, EVA 3000, EVA 6000 and

EVA 8000 arrays needed to be upgraded to the new format used by

Matrix Server.

• Defect 12567. When fabric fencing was configured with Cisco switches

running the 2.1b firmware, Matrix Server did not fence the correct

node.

• Defect 12647. LUNs on HDS Thunder storage could not be imported

into the matrix because extraneous underscores appeared in the UIDs

used by Matrix Server. The UID format was corrected in Matrix Server

3.1; however, when Matrix Server 3.1 was installed, the old UID

format was not recognized and the server was prevented from joining

the matrix.

• Defect 12684. Filesystems sometimes did not display as “mounted” on

the Management Console.

• Defect 12689. When the cluster was started or stopped, or during

failure conditions, the administrative interface could be set to unicast

mode unnecessarily.

• Defect 12704. The quotas “Select Users/Groups to Add” window did

not include a scrollbar when a search returned a large number of

users.

• Defect 12753. On servers configured with no swap space, the Matrix

Server mxperfd process continually failed and was then restarted,

which could eventually fill the root filesystem to capacity with

debugging information.

• Defect 12787. A locking problem caused the system to deadlock.

• Defect 12794. If a Performance Dashboard was opened and then

closed, the performance collection infrastructure would incorrectly