|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Cluster 3.3 With Network-Attached Storage Device Manual Oracle Solaris Cluster|
This section includes only restrictions and requirements that have a direct impact on the procedures in this chapter. For general support information, contact your Sun service provider.
This section describes the following requirements.
Sun Cluster uses the HTTP administrative access to support fencing. Sun Cluster automatically removes file system write permission for a node that has left the cluster, and grants file system write permission for a node that has just joined the cluster. These actions ensure that a node that departed the cluster can no longer modify data. You must have the administrator login and password. You need these items when you are configuring the device in the cluster.
Cluster nodes are configured with Solaris Internet Protocol Multipathing (IPMP).
The Network Appliance NAS device requires the SUNWzlib package to run on Sun Cluster. If you installed the End User Solaris Software Group on your cluster, you must add the SUNWzlib package using the pkgadd command.
# pkgadd SUNWzlib
Directories must be exported to all cluster nodes. When exporting Network Appliance NAS directories for use with the cluster, you must use the form rw=nodename1;nodename2 to specify access to the directories. You make these entries in the exports file on the NAS device.
When you configure your Network Appliance NAS device for use with Oracle Real Application Clusters (RAC), you must meet the following requirements.
You must configure the Network Appliance NAS device with fencing support in order to guarantee data integrity.
You must create a volume on each Network Appliance NAS device for storing Oracle database files, namely:
Online redo log files
Archived redo log files
The directory that contains Oracle data files for the cluster
The Oracle home directory that is to be mounted on each node
You must ensure that the volume is exported without the nosuid option.
The administrator has the option of deciding whether to use the Network Appliance NAS device as a quorum device.
Note - You do not need to configure a NAS device as a quorum device in a zone cluster environment. A quorum is not required for a zone cluster, because the zone cluster node role in the zone cluster membership directly depends on the global cluster node role on the machine that is hosting the zone cluster node.
If you boot devices in the wrong order, your nodes cannot find the quorum device. If a node should fail in this situation, your cluster might be unable to remain in service. If the cluster fails because the Network Appliance NAS quorum device was not available, bring up the NAS device. After that action completes, boot the cluster.
The Network Appliance NAS device must be located on the same network as the cluster nodes. If a Network Appliance NAS quorum device is not located on the same network as the cluster nodes, the quorum device is at risk of not responding at boot time within the timeout period, causing the cluster boot up to fail due to lack of quorum.
It is strongly recommended that you use a Network Appliance clustered filer. Clustered filers provide high availability with respect to the filer data and do not constitute a single point of failure in the cluster.
It is strongly recommended that you use the network time protocol (NTP) to synchronize time on the cluster nodes and the NAS device. Refer to your Network Appliance documentation for instructions about how to configure NTP on the NAS device. Select at least one NTP server for the NAS device that also serves the cluster nodes.
When configuring a Network Appliance NAS device as a quorum device, you can only add the quorum device when all cluster nodes are operating and communicating with the Network Appliance NAS device.