2.6.5 Other Restrictions

• In the event of a power failure that brings down the entire cluster, user intervention is required to restart the cluster. The administrator must determine the last node that went down (by examining /var/adm/messages) and run scadmin startcluster on that node. Then the administrator must run scadmin startnode on the other cluster nodes to bring the cluster back online.

• Sun Cluster does not support the use of the loopback file system (lofs) on Sun Cluster nodes.

• Do not run client applications on the Sun Cluster nodes. Because of local interface group semantics, a switchover or failover of a logical host may cause a TCP (telnet/rlogin) connection to be broken. This includes both connections that were initiated by the server hosts of the cluster, as well as connections that were initiated by client hosts outside the cluster.

• Do not run, on any Sun Cluster node, any processes that run in the real-time scheduling class.

• Do not access the /logicalhost directories from shells on any nodes. If you have shell connections to any /logicalhost directories when a switchover or failover is attempted, the switchover or failover will be blocked.

• The Sun Cluster HA administrative file system cannot be grown using the Solstice DiskSuite growfs(1M) command.

• File system quotas are not supported in Sun Cluster.

• Logical network interfaces are reserved for use by Sun Cluster.

• Sun Prestoserve is not supported. Prestoserve works within the host system, which means that any data contained in the Prestoserve memory would not be available to the Sun Cluster sibling in the event of a switchover.