Service and Application Restrictions

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

• Do not configure cluster nodes as NIS or NIS+ servers. However, cluster nodes can be NIS or NIS+ clients.

• Do not use a Sun Cluster configuration to provide a highly available boot or installation service on client systems.

• Do not use a Sun Cluster configuration to provide an rarpd service.

• If you install an RPC service on the cluster, the service must not use the following program numbers: 100141, 100142, and 100248. These numbers are reserved for the Sun Cluster daemons rgmd_receptionist, fed, and pmfd, respectively. If the RPC service you install also uses one of these program numbers, you must change that RPC service to use a different program number.

• Currently, Sun StorEdge Network Data Replicator (SNDR) can only be used with HAStorage. This restriction only applies to the light weight resource group that includes the logical host that SNDR is using for replication. Application resource groups can still use HAStoragePlus with SNDR. You can use failover file system with HAStoragePlus and SNDR by using HAStorage for the SNDR resource group, and HAStoragePlus for the application resource group, where the HAStorage and HAStoragePlus resources point at the same underlying DCS device. A patch is being developed to enable SNDR to work with HAStoragePlus.

• Running high-priority process scheduling classes on cluster nodes is not supported. Processes that run in the time-sharing scheduling class with a high priority, or processes that run in the real-time scheduling class should not be run on cluster nodes. Sun Cluster software relies on kernel threads that do not run in the real-time scheduling class. Other time-sharing processes that run at higher-than-normal priority or real-time processes can prevent the Sun Cluster kernel threads from acquiring needed CPU cycles.