Chapter 3 Software Installation

This chapter describes how to install required software for Solaris software and PRIMECLUSTER on native machines.

The following procedures are explained here:

PRIMECLUSTER installation (overview)
Installation and setup of related software
Application installation and environment setup

See

If using PRIMECLUSTER with an Oracle VM Server for SPARC environment, refer to "Chapter 14 Using PRIMECLUSTER in Oracle VM Server for SPARC Environment."

If using PRIMECLUSTER with Oracle Solaris Kernel Zones environment, refer to "Chapter 15 Using PRIMECLUSTER in Oracle Solaris Kernel Zones Environment ."

If using PRIMECLUSTER with an Oracle Solaris Zones environment, refer to "Chapter 16 Using PRIMECLUSTER in Oracle Solaris Zones Environment."

Note

When mirroring the system disk using GDS in a ZFS boot environment, there are some notes on the installation of the operating system. For details, see "PRIMECLUSTER Global Disk Services Configuration and Administration Guide".
PRIMECLUSTER is guaranteed to work with a maximum umask value of "022." Do not modify the umask value.
Change the system locale after setting up the shutdown facility.
When changing the system locale before setting up the shutdown facility (for example, changing the system locale to EUC in the Oracle Solaris 11 environment), the FJSVcluster format message output in the /var/adm/messages file at the time of setting up the shutdown facility may become garbled. If this phenomenon occurs, restart the system to correct the garbled message.
For immediate cluster failover if an I/O device where the system volume is placed fails
If an I/O device where the system volume is placed fails, a cluster failover does not occur and the system operation may continue based on the data stored on the memory.
When using the ZFS file system for the system volume, if you want PRIMECLUSTER to trigger a cluster failover by panicking a node in the event that an I/O device where the system volume is placed fails, perform the following settings:
Settings
Set failmode in ZFS root pool settings to "panic".
Example:
```
# zpool set failmode=panic rpool
```
However, an immediate cluster failover may not become available due to taking time for an I/O error to reach the file system. The regularly writing to the system volume enhances the detection frequency of I/O error.