Veritas Storage Foundation 5.1 SP1 Cluster File System Release Notes (5900-1509, April 2011)

to contact a majority of the coordination points or the lowest node itself
unexpectedly panics during the race, then all the nodes in that sub-cluster will
panic. [1965954]
Coordination Point agent does not provide detailed log message
for inaccessible CP servers
The Coordination Point agent does not log detailed information of the CP servers
that are inaccessible. When CP server is not accessible, the agent does not mention
the UUID or the virtual IP of the CP server in the engine log. [1907648]
Preferred fencing does not work as expected for large clusters
in certain cases
If you have configured system-based or group-based preferred fencing policy,
preferred fencing does not work if all the following cases are true:
■ The fencing setup uses customized mode with one or more CP servers.
■ The application cluster has more than eight nodes.
■ The node weight for a single node (say galaxy with node id 0) is more than the
sum total of node weights for the rest of the nodes.
■ A network fault occurs and the cluster partitions into two with the single node
(galaxy) on one part and the rest of the nodes on the other part.
Under such circumstances, for group-based preferred fencing, the single node
panics even though more high priority services are online on that node. For
system-based preferred fencing, the single node panics even though more weight
is assigned to the node. [2161816]
See the Veritas Storage Foundation Cluster File System Administrator's Guide for
more information on preferred fencing.
Server-based I/O fencing fails to start after configuration on
nodes with different locale settings
On each (application cluster) node, the vxfen module retrieves and stores the list
of the UUIDs of coordination points. When different nodes have different locale
settings, the list of UUIDs on one (application) node does not match with that of
the other (application) nodes. Hence, I/O fencing does not start after configuration.
[2112742]
Workaround: Start I/O fencing after fixing the locale settings to use the same
values on all the (application) cluster nodes.
43Storage Foundation Cluster File System Release Notes
Known issues