3.4.0 Matrix Server Release Notes

PolyServe Matrix Server Release Notes 28
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
Matrix File Serving Solution Pack for CIFS
The following issues affect the operation of the Matrix File Serving
Solution Pack for CIFS.
Bug
Description
4507 File shares with duplicate names are problematic
If a Matrix File Share and a Virtual File Share are created with
the same name, the automated monitors can become confused
about which File Share they are monitoring. This situation can
cause unexpected failover behavior or can cause a File Share to
point to the wrong resource.
Workaround. If a Matrix File Share and a Virtual File Share have
the same name, they must be configured identically.
5344
Disabling a server does not disable Matrix File Shares
When a server is disabled, the Matrix File Shares on that server
remain active.
Workaround. Either disable the Matrix File Shares one-at-a-
time, or disable the LanManServer service.
6555
IP address may be set to 0.0.0.0 when Autofailback policy is
used
When a Virtual File Server is configured with the Autofailback
policy, MxFS for CIFS places an IP address on the newly booted
node selected for the failback operation. Under certain
circumstances, the IP address is incorrectly set to 0.0.0.0, making
the address inaccessible from the network.
This problem has been observed when Dell OpenManage is
installed but may also occur with other applications. For Dell
OpenManage, setting the “Systems Management Data
Manager” service for “Manual” start instead of the default
Autostart” avoids the problem.
Another solution is to configure the Virtual File Server with the
default Nofailback policy. This policy forces the CIFS virtual
server to stay on the active node even when the primary (or
other higher-order backup nodes) reboot.