HP StorageWorks Clustered File System 3.6.0 Windows Storage Server Edition (server/software bundle) Release Notes (403107-008, February 2008)

Custom setting f
or GcT rimLevel should be removed [1944 2]
In previous rel
eases of HP Clustered Fi le System, there have been recommendations to add a registry
setting for GcT
rimLevel to restrict the amount of Windows pool memory consumed by the product. In
Clustered Fil
e
System 3.6, a new tunable GcTrimMax has been added that caps the maximum number of
FCBs that the product will cache (the default is 10,000). With the new settings, the defaults should be
suitable for all but the m ost unusual workloads. H P advises customers to remove any custom setting of
GcTrimLev el when upgrading to Clustered File System 3.6.
Open issues and workarounds for HP Clustered File System
File Serving (FS) Option
The following issues affect the operation of FS Option.
File shares
with duplicate names are problematic [4507]
If a Cluster File Share and a Virtual File S h are are created with the same name, the automated monitors
can
become c
onfused about which File Share they are monitoring. This situation can cause unexpected
failover be
havior or can cause a File Share to point to the wrong resource.
Workaround—Avoid creating Cluster File Shares and Virtual File Shares with the same name.
Disabling a server does not disable Cluster File S hares [5344]
When a server is disabled, the Cluster File Shares on that server remain active.
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 [6555]
When a Virtual File Server is configured with the Autofailback policy, HP Clustered File System FS
Option places an IP address on the newly booted node selected for the failback operation. Under
certain c
ircumstances, the IP address is incorrectly set to 0.0.0.0, making the address inaccessible
from the n
etwork.
This problem has been observed when Dell OpenManage is installed but may also oc cur with other
applications. For D ell OpenManage, setting the “Systems Management Data Manager” ser vice for
“Manual” start instead of the default “Autostart” avoids the problem.
Another solution is to con figure 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
contro
lled manual failback after the OS has finished booting. A subsequent failure of the a ctive nod e
resul
ts
in a correct failback without exhibiting the problem, if the target node is already up and running in
astab
le
state, and is not in the process of booting.
Creating Virtual File Server with ALL_SERVERS option can cause confusion
[9564]
When cre ating Virtual File Servers with the ALL_SERVERS comm and-line option:
• Any ser vers added to the cluster at a later time will automatically be added to the Virtual File
Server.
• The HP CFS Management Console does not provide a way to identify Virtual File Servers created
with the ALL_SERVERS option.
Servers a d d ed to a Virtual File Ser ver with the ALL_SERVERS option cannot be removed from the
configuration via the Ma nagement Console. You will need to use the mx vfs update command and
14