sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
Chapter 6 # Installing the Software on the Master-Eligible Nodes After you have set up the installation environment, you are ready to install the Solaris operating system and the Foundation Services manually on the master-eligible nodes of the cluster. The master-eligible nodes take on the roles of master node and vice-master node in the cluster. For more information about the types of nodes, see the Netra High Availability Suite Foundation Services 2.1 6/03 Overview. To install and configure the Foundation Services manually on the master-eligible nodes of your cluster, see the following sections: Defining Disk Partitions on the Master-Eligible Nodes Installing the Solaris Operating System on the Master-Eligible Nodes Setting Up the Master-Eligible Nodes Installing the Foundation Services on the Master-Eligible Nodes Configuring the Master-Eligible Node Addresses Configuring the Foundation Services on the Master-Eligible Nodes Setting Up File Systems on the Master-Eligible Nodes Installing the Man Pages on the Master-Eligible Nodes Starting the Master-Eligible Nodes Note - Do not use the `nhcmmstat` or `scmadm` tools to monitor the cluster during the installation procedure. Use these tools only after the installation and configuration procedures have been completed on all nodes. ## Defining Disk Partitions on the Master-Eligible Nodes The master-eligible nodes store current data for all nodes in the cluster, whether the cluster has diskless nodes or dataless nodes. One master-eligible node is to be the master node, while the other master-eligible node is to be the vice-master node. The vice-master node takes over the role of master in case the master node fails or is taken offline for maintenance. Therefore, the disks of both these nodes must have exactly the same partitions. Create the disk partitions of the master-eligible node according to the needs of your cluster. For example, the disks of the master-eligible nodes must be configured differently if diskless nodes are part of the cluster. The following table lists the space requirements for example disk partitions of master-eligible nodes in a cluster with diskless nodes. Table 6-1 Example Disk Partitions of Master-Eligible Nodes
Disk Partition | File System Name | Description | Example Size
--- | --- | --- | ---
0 | `/` | The root file system, boot partition, and volume management software. This partition must be mounted with the `logging` option. | 2 Gbytes minimum
1 | `/swap` | Minimum size when physical memory is less than 1 Gbyte. | 1 Gbyte
2 | `overlap` | Entire disk. | Size of entire disk
3 | `/export` | Exported file system reserved for diskless nodes. This partition must be mounted with the `logging` option. This partition is further partitioned if diskless nodes are added to the cluster. | 1 Gbyte + 100 Mbytes per diskless node
4 | `/SUNWcgha/local` | This partition is reserved for NFS status files, services, and configuration files. This partition must be mounted with the `logging` option. | 2 Gbytes
5 | Reserved for Reliable NFS internal use | Bitmap partition reserved for the `nhcrfsd` daemon. This partition is associated with the `/export` file system. | See Table 6-2
6 | Reserved for Reliable NFS internal use | Bitmap partition reserved for the `nhcrfsd` daemon. This partition is associated with the `/SUNWcgha/local` file system. | See Table 6-2
7 | `/mypartition` | For any additional applications. | The remaining space
For replication, create a bitmap partition for each partition containing an exported, replicated file system on the master-eligible nodes. The size of the bitmap partition must be equal to 512 bytes + 1 bit per 32 Kbytes of the data device size. In this example, the bitmaps are created on partitions 5 and 6. The bitmap partition sizes can be as shown in the following table. Table 6-2 Example Bitmap Partitions
File System Name | Bitmap Partition | File System (Mbytes) | Bitmap File (Kbytes) | Bitmap Size (Block)
--- | --- | --- | --- | ---
`/export` | `/dev/rdsk/c0t0d0s5` | 2000 | 8512 | 18
`/SUNWcgha/local` | `/dev/rdsk/c0t0d0s6` | 1512 | 6512 | 14
4. For information, see the Sun StorEdge Availability Suite 3.1 Remote Mirror Software Installation Guide in the Sun StorEdge Availability Suite 3.1 documentation set. Note - In a cluster without diskless nodes, the `/export` file system and the associated bitmap partition are not required. ## Installing the Solaris Operating System on the Master-Eligible Nodes To install the Solaris operating system on each master-eligible node, use the Solaris JumpStart tool on the installation server. The Solaris JumpStart tool requires the Solaris distribution to be on the installation server. For information about creating a Solaris distribution, see Preparing the Installation Environment. ### To Install the Solaris Operating System on the Master-Eligible Nodes Log in to the installation server as superuser. Create the Solaris JumpStart environment on the installation server by using the appropriate document for the Solaris release: Solaris 8 Advanced Installation Guide Solaris 9 Installation Guide You can access these documents on `http://docs.sun.com`. In the `/etc/hosts` file, add the names and IP addresses of the master-eligible nodes. Share the Solaris-distribution-dir and Jumpstart-dir directories by adding these lines to the `/etc/dfs/dfstab` file:
       share -F nfs -o ro,anon=0 Solaris-distribution-dir
       share -F nfs -o ro,anon=0 Jumpstart-dir
5. Solaris-distribution is the directory that contains the Solaris distribution. Jumpstart-dir is the directory that contains the Solaris JumpStart files. Share the directories that are defined in the `/etc/dfs/dfstab` file:
       # shareall
6. Change to the directory where the `add_install_client` command is located:
       # cd Solaris-dir/Solaris_x/Tools
9. Solaris-dir is the directory that contains the Solaris installation software. This directory could be on a CD-ROM or in an NFS-shared directory. `x` is `8` or `9` depending on the Solaris version installed. Run the `add_install_client` command for each master-eligible node: For information, see the `add_install_client`(1M) man page. Connect to the console of each master-eligible node. At the `ok` prompt, boot each master-eligible node using the `net` device alias:
       ok> boot net - install
   If the installation server is connected to the second Ethernet interface, type:
       ok> boot net2 - install
This command installs the Solaris operating system on the master-eligible nodes.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems