JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Software Installation Guide     Oracle Solaris Cluster
search filter icon
search icon

Document Information


1.  Planning the Oracle Solaris Cluster Configuration

Finding Oracle Solaris Cluster Installation Tasks

Planning the Oracle Solaris OS

Guidelines for Selecting Your Oracle Solaris Installation Method

Oracle Solaris OS Feature Restrictions

Oracle Solaris Software Group Considerations

System Disk Partitions

Guidelines for the Root (/) File System

Guidelines for the /globaldevices File System

Volume Manager Requirements

Example - Sample File-System Allocations

Guidelines for Non-Global Zones in a Global Cluster

SPARC: Guidelines for Sun Logical Domains in a Cluster

Planning the Oracle Solaris Cluster Environment


Software Patches

Public-Network IP Addresses

Console-Access Devices

Logical Addresses

Public Networks

Quorum Servers

NFS Guidelines

Service Restrictions

Network Time Protocol (NTP)

Oracle Solaris Cluster Configurable Components

Global-Cluster Name

Global-Cluster Voting-Node Names and Node IDs

Zone Names

Private Network

Private Hostnames

Cluster Interconnect

Transport Adapters

Transport Switches

Global Fencing

Quorum Devices

Zone Clusters

Global-Cluster Requirements and Guidelines

Zone-Cluster Requirements and Guidelines

Guidelines for Trusted Extensions in a Zone Cluster

Planning the Global Devices, Device Groups, and Cluster File Systems

Global Devices

Device Groups

Cluster File Systems

Choosing Mount Options for Cluster File Systems

UFS Cluster File Systems

VxFS Cluster File Systems

Mount Information for Cluster File Systems

Planning Volume Management

Guidelines for Volume-Manager Software

Guidelines for Solaris Volume Manager Software

Guidelines for Veritas Volume Manager Software

File-System Logging

Mirroring Guidelines

Guidelines for Mirroring Multihost Disks

Guidelines for Mirroring the Root Disk

2.  Installing Software on Global-Cluster Nodes

3.  Establishing the Global Cluster

4.  Configuring Solaris Volume Manager Software

5.  Installing and Configuring Veritas Volume Manager

6.  Creating a Cluster File System

7.  Creating Non-Global Zones and Zone Clusters

8.  Installing the Oracle Solaris Cluster Module to Sun Management Center

9.  Uninstalling Software From the Cluster

A.  Oracle Solaris Cluster Installation and Configuration Worksheets


Planning the Oracle Solaris OS

This section provides the following guidelines for planning Solaris software installation in a cluster configuration.

For more information about Solaris software, see your Solaris installation documentation.

Guidelines for Selecting Your Oracle Solaris Installation Method

You can install Solaris software from a local DVD-ROM or from a network installation server by using the JumpStart installation method. In addition, Oracle Solaris Cluster software provides a custom method for installing both the Solaris OS and Oracle Solaris Cluster software by using the JumpStart installation method. If you are installing several cluster nodes, consider a network installation.

See How to Install Solaris and Oracle Solaris Cluster Software (JumpStart) for details about the scinstall JumpStart installation method. See your Solaris installation documentation for details about standard Solaris installation methods.

Oracle Solaris OS Feature Restrictions

Consider the following points when you plan the use of the Solaris OS in an Oracle Solaris Cluster configuration:

Oracle Solaris Software Group Considerations

Oracle Solaris Cluster 3.3 5/11 software requires at least the End User Solaris Software Group (SUNWCuser). However, other components of your cluster configuration might have their own Solaris software requirements as well. Consider the following information when you decide which Solaris software group you are installing.

Tip - To avoid the need to manually install Solaris software packages, install the Entire Solaris Software Group Plus OEM Support.

System Disk Partitions

Add this information to the appropriate Local File System Layout Worksheet.

When you install the Solaris OS, ensure that you create the required Oracle Solaris Cluster partitions and that all partitions meet minimum space requirements.

To meet these requirements, you must customize the partitioning if you are performing interactive installation of the Solaris OS.

See the following guidelines for additional partition planning information:

Guidelines for the Root (/) File System

As with any other system running the Solaris OS, you can configure the root (/), /var, /usr, and /opt directories as separate file systems. Or, you can include all the directories in the root (/) file system.

The following describes the software contents of the root (/), /var, /usr, and /opt directories in an Oracle Solaris Cluster configuration. Consider this information when you plan your partitioning scheme.

Guidelines for the /globaldevices File System

Oracle Solaris Cluster software offers two choices of locations to host the global-devices namespace:

This section describes the guidelines for using a dedicated partition. This information does not apply if you instead host the global-devices namespace on a lofi.

The /globaldevices file system is usually located on your root disk. However, if you use different storage on which to locate the global-devices file system, such as a Logical Volume Manager volume, it must not be part of a Solaris Volume Manager shared disk set or part of a VxVM disk group other than a root disk group. This file system is later mounted as a UFS cluster file system. Name this file system /globaldevices, which is the default name that is recognized by the scinstall(1M) command.

Note - No file-system type other than UFS is valid for the global-devices file system. Do not attempt to change the file-system type after the global-devices file system is created.

However, a UFS global-devices file system can coexist on a node with other root file systems that use ZFS.

The scinstall command later renames the file system /global/.devices/node@nodeid, where nodeid represents the number that is assigned to a Solaris host when it becomes a global-cluster member. The original /globaldevices mount point is removed.

The /globaldevices file system must have ample space and ample inode capacity for creating both block special devices and character special devices. This guideline is especially important if a large number of disks are in the cluster. Create a file system size of at least 512 Mbytes and a density of 512, as follows:

# newfs -i 512 globaldevices-partition

This number of inodes should suffice for most cluster configurations.

Volume Manager Requirements

If you use Solaris Volume Manager software, you must set aside a slice on the root disk for use in creating the state database replica. Specifically, set aside a slice for this purpose on each local disk. But, if you have only one local disk on a Solaris host, you might need to create three state database replicas in the same slice for Solaris Volume Manager software to function properly. See your Solaris Volume Manager documentation for more information.

If you use Veritas Volume Manager (VxVM) and you intend to encapsulate the root disk, you need to have two unused slices that are available for use by VxVM. Additionally, you need to have some additional unassigned free space at either the beginning or the end of the disk. See your VxVM documentation for more information about root disk encapsulation.

Example – Sample File-System Allocations

Table 1-2 shows a partitioning scheme for a Solaris host that has less than 750 Mbytes of physical memory. This scheme is to be installed with the End User Solaris Software Group, Oracle Solaris Cluster software, and the Oracle Solaris Cluster HA for NFS data service. The last slice on the disk, slice 7, is allocated with a small amount of space for volume-manager use.

This layout allows for the use of either Solaris Volume Manager software or VxVM software. If you use Solaris Volume Manager software, you use slice 7 for the state database replica. If you use VxVM, you later free slice 7 by assigning the slice a zero length. This layout provides the necessary two free slices, 4 and 7, as well as provides for unused space at the end of the disk.

Table 1-2 Example File-System Allocation

Size Allocation
Remaining free space on the disk after allocating space to slices 1 through 7. Used for the Solaris OS, Oracle Solaris Cluster software, data-services software, volume-manager software, Sun Management Center agent and Oracle Solaris Cluster module agent packages, root file systems, and database and application software.
512 Mbytes for the Solaris OS.

512 Mbytes for Oracle Solaris Cluster software.

The entire disk.
The Oracle Solaris Cluster software later assigns this slice a different mount point and mounts the slice as a cluster file system. If you choose to use a lofi device instead of a dedicated partition, leave slice 3 as Unused.
Available as a free slice for encapsulating the root disk under VxVM.
volume manager
Used by Solaris Volume Manager software for the state database replica, or used by VxVM for installation after you free the slice.

Guidelines for Non-Global Zones in a Global Cluster

For information about the purpose and function of Solaris zones in a cluster, see Support for Oracle Solaris Zones in Oracle Solaris Cluster Concepts Guide.

For guidelines about configuring a cluster of non-global zones, see Zone Clusters.

Consider the following points when you create a Solaris 10 non-global zone, simply referred to as a zone, on a global-cluster node.

SPARC: Guidelines for Sun Logical Domains in a Cluster

Consider the following points when you create a Sun Logical Domains (LDoms) I/O domain or guest domain on a physically clustered machine that is SPARC hypervisor capable:

For more information about Sun Logical Domains, see the Logical Domains (LDoms) 1.0.3 Administration Guide.