3.5.1 Matrix Server Release Notes

PolyServe Release Notes 18
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
15103 Deadlock can occur if a node is a client for an NFS filesystem
A node running Matrix Server should not be configured as a
client for an NFS filesystem. Doing this can cause a deadlock
situation on the node.
15782 License file is not read immediately when installed out of
sequence during upgrade
The upgrade procedure specifies when the license file should be
installed. If the file is installed at a later point, it may take up to
15 minutes for the new license to be refreshed and virtual hosts
to become available. To force the license to be refreshed
immediately, take one of these steps:
Reboot the node or restart Matrix Server after the license file
is installed.
Connect the Management Console to the node and run the
Management Console “Refresh License” option. (If the
Management Console is connected to a different node, the
“Refresh License” option will fail to refresh the license.)
16056 Configure Matrix window shows local device names when
third-party MPIO is used
When third-party MPIO is used and you are configuring
membership partitions on the Configure Matrix window, the
available devices are specified by their local device names
instead of the names assigned by the third-party MPIO solution.
(Your MPIO solution should allow you to map the local names
to the MPIO names.)
Although the Configure Matrix window displays the local
device names, Matrix Server will use the third-party MPIO
device names when it is configured.
Defect
Description