The following Sun Cluster 3.0 12/01 Release Notes restriction has been changed.
Original:
Storage devices with more than two physical paths to the enclosure - More than two paths are not supported. The Sun StorEdge A3500, for which two paths are supported to each of two nodes, is an exception.
Revised:
Storage devices with more than two physical paths to the enclosure - More than two paths are not supported. There are two exceptions: the Sun StorEdgeTM A3500, for which two paths are supported to each of two nodes, and EMC storage devices that use EMC PowerPath software.
The following cluster-file-system restriction in the Sun Cluster 3.0 12/01 Release Notes has been revised to add clarification.
Original:
The cluster file system does not support any of the file system features of Solaris by which one would put a communication end-point in the file system name space. Therefore, you cannot create a UNIX domain socket whose name is a path name into the cluster file system, nor can you create fifos or named pipes, nor should you attempt to use fattach.
Revised:
The cluster file system does not support any of the file-system features of Solaris software by which one would put a communication end-point in the file-system name space. Therefore, although you can create a UNIX domain socket whose name is a path name into the cluster file system, the socket would not survive a node failover. In addition, any fifos or named pipes you create on a cluster file system would not be globally accessible, nor should you attempt to use fattach from any node other than the local node.