Oracle® Solaris Cluster Software Installation Guide

Exit Print View

Updated: September 2014, E39580-02

Service Restrictions

Observe the following service restrictions for Oracle Solaris Cluster configurations:

  • Routers Do not configure cluster nodes as routers (gateways) due to the following reasons:

    • Routing protocols might inadvertently broadcast the cluster interconnect as a publicly reachable network to other routers, despite the setting of the IFF_PRIVATE flag on the interconnect interfaces.

    • Routing protocols might interfere with the failover of IP addresses across cluster nodes that impact client accessibility.

    • Routing protocols might compromise proper functionality of scalable services by accepting client network packets and dropping them, instead of forwarding the packets to other cluster nodes.

  • NIS+ servers – Do not configure cluster nodes as NIS or NIS+ servers. There is no data service available for NIS or NIS+. However, cluster nodes can be NIS or NIS+ clients.

  • Install servers – Do not use an Oracle Solaris Cluster configuration to provide a highly available installation service on client systems.

  • RARP Do not use an Oracle Solaris Cluster configuration to provide an rarpd service.

  • Remote procedure call (RPC) program numbers If you install an RPC service on the cluster, the service must not use any of the following program numbers:

    • 100141

    • 100142

    • 100248

    These numbers are reserved for the Oracle Solaris Cluster daemons rgmd_receptionist, fed, and pmfd, respectively.

    If the RPC service that you install also uses one of these program numbers, you must change that RPC service to use a different program number.

  • Scheduling classes Oracle Solaris Cluster software does not support the running of high-priority process scheduling classes on cluster nodes. Do not run either of the following types of processes on cluster nodes:

    • Processes that run in the time-sharing scheduling class with a high priority

    • Processes that run in the real-time scheduling class

    Oracle Solaris 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 Oracle Solaris Cluster kernel threads from acquiring needed CPU cycles.