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

server has the temporar y address, it cannot rejoin the cluster, as HP Clustered Gateway expects the server
to have the DHCP address.
During this process, the cluster con figuration m ight be destroyed on the rebooted server; however, the
configuration can be restored by importing it from another no de in the cluster (or by exporting the
configuration from a good node to the rebooted server).
To avoid this problem, use static IP addresses for the servers that will be in the cluster.
Third-party M PIO software must discover d evices [7519]
When third-p
arty MPIO software is used, it must discover and present storage devices to the operating
system befor
e
HP Clustered File System is configured or started.
If HP Cluster
ed
File System is started and the third-party MPIO software has not previously discovered the
devices, HP Clustered File System makes a “best effort” to discover them. In some cases, HP Clustered
Fi le System initiates a single reboot. HP Clustered File System does not start if it cannot discover the
devices. Th
e
administrator must then determine why the MPIO devices have not been discovered and
resolve the issue.
HP Clustered Gateway Installer does not find saved configuration [7551]
When HP Clustered File System is uninstalled, you can save the cluster configuration. If you then reinstall
HP Clustered File System in a different location, the Installer will not find the saved configuration. To avoid
this
problem, reinstall HP Clustered File System in its original location. The Installer will then find the saved
configuration and apply it to the new installation of HP Clustered File System.
If you need to install HP Clustered File System in a new location, mov e the saved configuration files to
the
new location before the HP Clustered File System installation.
F ilesy stem resi ze does not work correctly with mount points [7591]
The HP Ma
nagement Console includes an option to extend the size of a filesystem. After a filesystem is
extended, HP Clustered File System attempts to re assign the drive letters or mount points associated with
the
filesystem. HP Clustered File System reassigns drive letters correctly; however, it fails to reassign mount
points. Re-create the appropriate mount points manually after the extend operation is complete.
To re-create the mount points, first m anually delete the old mount points (the empty directories on the local
NTFS vo
lumes of each node). Next, recreate the empty directories and then use the HP Management
Console to reassign the mount points m anually.
Virtual host can cause route change [8290]
When a virtual host is instantiated, it uses the network mask of the interface upon which it is activa ted.
This can cause an unexpected route change if the virtual host address was intended for some other
interface on another network, or if the virtual host address is mistyped.
For example, the following command add s the 10.10.1.100 address on the 10.11.1.1 interface:
mx vhost add 10.10.1.100 10.11.1.1
If the 10.11.1.1 interface had a netmask of 255.255.0 .0, then the traffic for the 10.10/16 subnet would
be
directly routed to the 10.11/16 network for this server, rather than being routed to a gateway on
the
10.11/16 network.
URL i
n
HTTP service monitor can cause virtual host to fail [8335]
The U
RL
assigned to an HT T P service monitor should not reference the virtual host with which the
HTT
P
service monitor is associated. If the virtual host is down, the HT T P service monitor cannot make
a
connection to the virtual host address and will also be down. A down service monitor on a virtual
host then tends to keep the virtual host from ever being instantiated.
HP StorageWorks Clustered File System 3.6.0 WSS Edition (server/software bundle) release notes
9