4.1.0 HP Polyserve Matrix Server Release Notes (T5392-96068, October 2010)

HP PolyServe Software for Windows File Serving
The following considerations affect HP PolyServe Software for Windows File Serving.
DescriptionNumber
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.
4507
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.
5344
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, HP PolyServe Software for
Windows File Serving 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.
The problem does not appear when the enable/disable commands are used in a controlled manual
failback after the OS has finished booting. A subsequent failure of the active node will result in a
correct failback without exhibiting the problem if the target node is already up and running in a
stable state and is not in the process of booting.
6555
Creating Virtual File Server with ALL_SERVERS option can cause confusion
When creating Virtual File Servers with the ALL_SERVERS command-line option, you should be
aware of the following:
• When a Virtual File Server is created with the command-line ALL_SERVERS option, any servers
added to the matrix at a later time will automatically be added to the Virtual File Server.
• The PolyServe Management Console does not provide a way to identify Virtual File Servers
created with the ALL_SERVERS option.
• Servers added to a Virtual File Server with the ALL_SERVERS option cannot be removed from
the configuration via the Management Console. Instead, you will need to use the mx vfs update
command and specify the individual servers that are to be included in the configuration. For
example, the following command removes node3 from a 4-node Virtual File Server.
mx vfs update myVFS node1 node2 node4
9564
Nodes crash after rebooting
When HP PolyServe Software for Windows File Serving is installed, nodes sometimes crash
immediately after rebooting. This is a known Microsoft Windows problem. If you are experiencing
crashes after rebooting servers, contact Microsoft and ask for the hotfix described in Knowledge
Base article 908249.
12758
22