1    Introduction

This manual describes how to install and configure the TruCluster Server product.

Before you begin the installation, read this manual, paying close attention to the chapters that deal with your type of installation. Becoming familiar with the general sequence of installation steps can save time and prevent later problems.

You cannot use Sysman to install or deinstall the TruCluster Server product or layered products on a cluster. Instead, use the mechanisms described in this manual and the Cluster Administration manual.

Your cluster can use either Memory Channel or local area network (LAN) hardware for the cluster interconnect. The Cluster Hardware Configuration manual contains the information needed to configure the Memory Channel or LAN hardware as the cluster interconnect. The procedures covered in this installation manual include the steps necessary to configure the interconnect software.

Notes

The procedures in this manual assume that each system's hardware and firmware are installed and configured as described in the Cluster Hardware Configuration manual. Do not begin the software installation until the hardware and firmware are installed and configured, and all storage and cluster interconnect hubs or switches are turned on.

Before you install TruCluster Server, read the Cluster Release Notes. If you are not familiar with the TruCluster Server architecture and terminology, read the Cluster Technical Overview manual.

This chapter provides the following information:

• New or changed installation features for Version 5.1B (Section 1.1)

• Installation types (Section 1.2)

• Installation commands (Section 1.3)

• Full installation overview (Section 1.4)

• License requirements (Section 1.5)

• TruCluster Server subsets (Section 1.6)

• Tru64 UNIX subsets (Section 1.7)

• General considerations (Section 1.8)

1.1    New or Changed Installation Features for Version 5.1B

The following list describes new or changed features for TruCluster Server Version 5.1B that affect installation or upgrade procedures:

• Parallel roll stages during a rolling upgrade.

  After performing the roll stage on the lead member, you can simultaneously roll as many as four members, depending on the cluster configuration. See Section 7.3.

• No-roll patching.

  If a short period of loss of cluster availability is acceptable, you can use the dupatch command to apply a patch clusterwide, rather than rolling the patch into each cluster member. See the Patch Kit Installation Instructions.

See the Cluster Technical Overview manual for the full list of new and changed features for TruCluster Server Version 5.1B.

1.2    Installation Types

There are two types of TruCluster Server installations:

full installation

Perform a full installation to create a new TruCluster Server cluster, or when you cannot (or choose not to) upgrade an existing cluster to TruCluster Server Version 5.1B. However, a full installation on an existing cluster will result in that cluster being unavailable during installation and application configuration.

upgrade installation

An upgrade installation preserves as much of the current configuration as possible. The type and version of your current product determine your upgrade path. Table 1-1 lists TruCluster products and their associated upgrade paths to TruCluster Server Version 5.1B.

Table 1-1:  Upgrade Paths to TruCluster Server Version 5.1B

1.3    Installation Commands

This section introduces the commands that create a cluster, add members to a cluster, remove members from a cluster, and perform a rolling upgrade:

clu_create

You run the clu_create command on a Tru64 UNIX system to create the first member of a cluster. See clu_create(8) and Chapter 4 for information on when and how to use the clu_create command.

clu_add_member

You run the clu_add_member command on a current member of a cluster to add a member to the cluster. See clu_add_member(8) and Chapter 5 for information on when and how to use the clu_add_member command.

clu_delete_member

You run the clu_delete_member command on a current member of a cluster to remove another member from the cluster. See clu_delete_member(8) and the Cluster Administration manual for information on when and how to use the clu_delete_member command.

clu_upgrade

You run the clu_upgrade command on specific members of the current cluster to perform a rolling upgrade. See clu_upgrade(8) and Chapter 7 for information on when and how to use the clu_upgrade command.

1.4    Full Installation Overview

The following list outlines the major steps needed to form a new TruCluster Server Version 5.1B cluster:

1. Using the information in the Cluster Hardware Configuration manual, configure system and storage hardware and firmware.

2. Selecting AdvFS file systems, install the Tru64 UNIX operating system on one or more disks. The disks are either private disks on the system that will become the first cluster member, or disks on a shared bus that the system can access.

   Note

   You install the Tru64 UNIX operating system on only one system. You do not have to install the operating system on each system that will become a cluster member.

3. Configure the Tru64 UNIX system, including network and time services. Load and configure the applications you plan to use in the cluster.

4. Load the TruCluster Server license and subsets.

5. Run the clu_create command to create a boot disk for the first cluster member and to create and populate the clusterwide ^{[Footnote 2]} root (/), /usr, and /var AdvFS file systems.

6. Halt the Tru64 UNIX system and boot the disk containing the first member's cluster boot partition. As the system boots, it forms a single-member cluster and mounts the clusterwide root (/), /usr, and /var file systems.

7. Log in as root and run the clu_add_member command to add members to the cluster. Boot each new member before adding the next.

1.5    License Requirements

There are no clusterwide licenses. You must install licenses on each cluster member.

For the first member, after installing and licensing Tru64 UNIX, load and register a TruCluster Server license (TCS-UA) to create a single-member cluster. You can load the TruCluster Server subsets without registering the TruCluster Server license, but you cannot create a cluster until you load and register a TruCluster Server license.

Each time you add an additional member to the cluster, you must register a TruCluster Server license. After you boot the new member, you must also register a Tru64 UNIX license (because the new member will use the Tru64 UNIX clusterwide root (/), /usr, and /var file systems). In addition, you must register any additional required application licenses on that member.

Note

You can boot a system that does not have a TruCluster Server license. The system joins the cluster and boots to multiuser mode, but only root can log in (with a maximum of two users). The cluster application availability (CAA) daemon, caad, is not started. The system displays a license error message reminding you to load the license. This policy enforces license checks while making it possible to boot, license, and repair a system during an emergency.

1.6    TruCluster Server Subsets

Table 1-2 lists the TruCluster Server subsets.

Table 1-2:  TruCluster Server Subset Contents

Table 1-3 lists the approximate disk space requirements, in megabytes (MB), for each TruCluster Server Version 5.1B subset in the root (/), /usr, and /var file systems on the Tru64 UNIX system. (Table 2-2 provides the minimum and recommended size requirements for the disks needed to create a cluster.)

Table 1-3:  TruCluster Server Subset Sizes

1.7    Tru64 UNIX Subsets

When you install Tru64 UNIX, you must select AdvFS as the file system type for the root (/), /usr, and /var file systems.

Regardless of the types of systems in the cluster, we strongly recommend that, unless prohibited by site policy, you load all subsets when installing the Tru64 UNIX operating system. You might add different systems at a later date, or you might install an application that has a dependency on a subset you did not install.

Note

If your cluster will contain different types of systems, make sure to load the optional Tru64 UNIX subsets needed to support different hardware configurations. For example, because keyboards and graphics cards require specific subsets to work properly, load all keyboard and font subsets.

You can add additional software subsets later, but, because you are dealing with only one system, it is easier to install them before you create a cluster. The Cluster Administration manual explains how to install subsets in an existing cluster.

1.8    General Considerations

Note the following general installation considerations:

• If you build your own kernels, be aware that in a cluster /vmunix is a context-dependent symbolic link (CDSL):

  /vmunix -> cluster/members/{memb}/boot_partition/vmunix
   
  

  Treat a CDSL as you do any other symbolic link: remember that copying a file follows the link, but moving a file replaces the link. If you move (instead of copy) a kernel to /vmunix, you replace the symbolic link with the actual file.

  The Cluster Technical Overview manual describes CDSLs; the Cluster Administration manual provides information on using and repairing CDSLs.

• The base operating system sets a minimum requirement for the amount of memory required to install Tru64 UNIX. In a cluster, each member must have at least 64 MB more than this minimum requirement. For example, if the base operating system requires 128 MB of memory, each system used in a cluster must have at least 192 MB of memory.

• TruCluster Server supports the UNIX file system (UFS) as a read-only file system clusterwide. That is, a member can mount a UFS file system and other members of the cluster have read-only access to it. However, a member can mount a UFS file system read/write, but only that member has read/write access to the file system (local use only). No other cluster members can access that file system. There is no failover if that member goes down.