3.6.0 Matrix Server Release Notes (5697-7087, February 2008)

PolyServe Matrix Server Release Notes 8

Open Issues and Workarounds

The following open issues affect PolyServe Matrix Server, MxDB for SQL

Server, including the Migration Utility, and MxFS for CIFS.

Matrix Server

The following issues affect Matrix Server.

Bug

Description

3636 Network interfaces are marked “Up” and then “Down”

repeatedly

The status of network interfaces may change between “Up” and

“Down” about every five seconds when there is only one server

in the matrix and no other IP address is available to ping. This

situation can occur when a two-node cluster loses a node or the

node is removed from service.

The problem appears only if the only gateway address to ping is

the interface IP address (that is, there is not a route to an outside

network). This scenario is unlikely to occur in practice, as there

will likely be many clients connected to the clustered server via

a client network.

However, the problem can occur in laboratory or test conditions.

To avoid the problem, add a router to the PAN network.

3793 Management Console does not display filesystems created

when Matrix Server was not running

If Matrix Server is not running while a PSFS filesystem is

created with the psfsformat -f command, the filesystem will not

be displayed on the PolyServe Management Console.

Workaround. Start the Matrix Server service before creating the

filesystem.