HP StorageWorks Clustered File System 3.2.1 Windows Storage Server Edition Administration Guide (February 2006)

Appendix B: Error and Event Log Messages 192
Cluster unable to take control of SAN, because a majority of
the membership partitions cannot be written or are corrupt,
possibly due to a SAN hardware failure or misconfiguration
and/or because servers have been excluded from the SAN. As a
result, some or all filesystem operations may be paused
throughout the cluster. In addition, filesystem mounts and
unmounts and disk imports and deports cannot be performed.
Ensure that all servers can access the membership partitions and have
write access to them.
If a membership partition is corrupt, another alert will specify its location.
See “Manage Membership Partitions with mprepair” on page 160 for
corrective actions.
Cluster unable to take control of SAN, because another
cluster that includes NN.NN.NN.NN currently controls the
SAN. Possibly a networking failure or misconfiguration has
partitioned these servers from the servers that control the
SAN, or possibly this cluster has been misconfigured to
share membership partitions with another cluster.
Check the cluster configuration and add the server if it is not currently a
member. If your site has more than one cluster, use mprepair to make
sure that this server is using the correct set of membership partitions.
Cluster unable to take control of SAN, because the servers
are unable to perform fencing operations, possibly due to a
networking or fencing hardware failure or misconfiguration.
As a result, some or all filesystem operations may be paused
throughout the cluster. In addition, filesystem mounts and
unmounts and disk imports and deports can not be performed.
HP Clustered File System is unable to exclude servers that have become
unresponsive, or to verify the fencing of servers that were previously
fenced and have not yet been rebooted. Possibly the fencing device is not
responding to the fencing request or the Ethernet connection to the
FibreChannel switch has failed. Also check for other networking or SAN
hardware problems. The servers should be rebooted as soon as possible.