HP Clustered FileSystem3.6.1 for Windows release notes (T4422-96003, September 2008)

HP Clustered File Sy

stem

FS Option for Windo ws

The following issues affect FS Option for Windows.

Issue

4507

5344

6555

Description

File shares with duplicate names are problematic

If a Cluster File Share and a Virtual File Share are created with the same name,

theautomated monitors canbecomeconfusedabout whichFileShare they are

monitoring. This situation can cause unexpected failover behavior or can cause a

File Sharetopoint to thewrong resource.

Workaround. If

Cluster File Share and a Virtual File Share have the same name,

they must be con

ﬁgured identically.

Disabling a ser ver does not disable Cluster File Shares

When a server is disabled, the Cluster File Shares on that ser ver remain a ctive.

Workaround. Either disable the Cluster File Shares one-at-a-time, or disable the

LanManServer service.

IP address may be set to 0.0.0.0 when Autofailback policy is used

When a Virtual File Server is conﬁgured with the Autofailback policy, FS Option

for Windows 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 inac cessible 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 conﬁgure 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

controlled manual failback after the OS has ﬁnished 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.

HP Clustered File S ystem 3.6 .1 f or Windows