Service and Application Restrictions

Note the following restrictions related to services and applications.

• Sun Cluster can be used to provide service for only those data services that either are supplied with Sun Cluster or set up using the Sun Cluster data services API.

• Do not configure the Sun Cluster nodes as mail servers, because sendmail(1M) is not supported in a Sun Cluster environment. No mail directories should reside on Sun Cluster nodes.

• Do not configure Sun Cluster systems as routers (gateways). If the system goes down, the clients cannot find an alternate router and recover.

• Do not configure Sun Cluster systems as NIS or NIS+ servers. Sun Cluster nodes can be NIS or NIS+ clients, however.

• A Sun Cluster configuration cannot be used to provide a highly available boot or install service to client systems.

• A Sun Cluster configuration cannot be used to provide highly available rarpd service.

• The Solaris interface groups feature is not supported on Sun Cluster, as it disrupts cluster switchover and failover behavior. You must disable Solaris interface groups on all cluster nodes. See "Disabling Solaris Interface Groups" for more information.

Default Port Numbers Reserved by Sun Cluster

Sun Cluster reserves certain port numbers for internal use. These port numbers are stored in the clustername.cdb file. Note the following reserved port numbers when planning your configuration, data services, and applications.

In addition, note that Solaris reserves ports 6000 to 6031 for UNIX Distributed Lock Manager (UDLM). UDLM is used with Oracle Parallel Server configurations.

Changing these port numbers is not allowed, except in the case of sm_configd and smad. To change the port numbers used by sm_configd or smad, edit the /etc/services files on all nodes. The files must be identical on all nodes. For all cases other than sm_configd and smad, you must change the application's port use rather than the cluster's.