5    Add Members

To add a member to the cluster, run the clu_add_member command on any current cluster member. This command creates directories and files for the new member in the clusterwide root (/), /usr, and /var file systems. It also labels and populates a boot disk for the new member. Because the current member must write to the potential member's boot disk, this boot disk must be accessible to the current member; for example, on a shared bus.

Notes

You do not need to install the base operating system on each new member. (However, you will have to register a Tru64 UNIX license on each new member after you boot it.)

When adding members, add one member and boot it into the cluster before running clu_add_member to add another member.

If you are using Fibre Channel storagesets for member boot disks, read the Fibre Channel chapter in the TruCluster Server Cluster Hardware Configuration manual.

Follow the directions in this chapter to add a member to a cluster. Table 5-1 lists the tasks in order and references necessary information.

Table 5-1:  Add Member Tasks

Task See
Gather the information for the new member. Chapter 2
Set the boot_osflags, boot_reset, and bus_probe_algorithm console variables on the system that will become the new member. Section 2.7
Update SRM firmware. Section 5.1
Verify that the Member Attributes checklist in Appendix A contains the dsk special file name, the DK console device name, and (if known) the WWID for the new member's boot disk. If you do not know the physical location of the new member's boot disk, locate it. [Footnote 4] Section 2.5.1, Section 3.7, Appendix A
Make sure that the system cannot boot during the installation. Section 5.2
Run the clu_add_member command on a current cluster member. Section 5.3
From the new member's console, boot the new member into the cluster. Section 5.4
Make on-disk backup copies of important configuration files Section 5.5

Note

Before running clu_add_member, make sure that the current member is fully configured (applications installed, network interfaces configured, network services configured, TruCluster Server license installed, and so forth).

If you fully configured the base operating system before running clu_create, you are now ready to run clu_add_member. If you did not fully configure the the base operating system before creating a cluster, we recommend that you finish configuring the cluster before running clu_add_member because the new member will inherit a large portion of its configuration from the current member.

5.1    Update SRM Firmware

New versions of Tru64 UNIX and TruCluster Server usually require new versions of the AlphaServer SRM firmware. Firmware updates are located on the Alpha Systems Firmware CD-ROM, which is included in the base operating system Software Distribution Kit. To determine whether you need to update firmware, see the TruCluster Server QuickSpecs and the firmware release notes for each type of system in the cluster. Update firmware as needed. You can find the latest version of the TruCluster Server QuickSpecs at the following URL: 

http://www.tru64unix.compaq.com/docs/pub_page/spds.html
 

5.2    Prevent the New Member from Booting During Installation

Halt or turn off the system that will become the new member. If halting the system:

  1. Set the auto_action console variable to halt: 

    >>> set auto_action halt
 

  2. Set the bootdef_dev console variable to an empty string: 

    >>> set bootdef_dev ""
 

The reason for these precautions is to make sure that the system cannot boot from the disk that clu_add_member will configure as the new member's boot disk.

5.3    Run the clu_add_member Command

Run the /usr/sbin/clu_add_member command. The command prompts for the information needed to create a single-member cluster. Answer the prompts using the information from the checklists in Appendix A. The command also provides online help for each question. To display the relevant help message, enter help or a question mark, ?, at a prompt.

If the cluster member on which you run the clu_add_member command was configured for use the LAN interconnect, the clu_add_member command prompts you for a physical cluster interconnect device name for the LAN interconnect. You have the following options:

Note

If you specify the device name of a NetRAIN device that is defined as the physical cluster interconnect device for the member on which you are running the clu_add_member command, the command prompts you to indicate whether you intend to use an identical NetRAIN device (same device name and same participating adapters) on the member you are adding. If you respond "yes," the clu_add_member command defines the device as the cluster interconnect device in the ics_ll_tcp stanza of the /etc/sysconfigtab file.

The clu_add_member command then creates an IP name for the physical cluster interconnect device of the form membermember-ID-icstcp0 and by default offers an IP address of 10.1.0.member-ID for this device.

See Table C-2 for a list of /etc/sysconfigtab attributes written by the clu_add_member command to define the cluster interconnect.

The clu_add_member command configures the new member's boot disk, adds and modifies files in the clusterwide file systems, and gives you the option of loading the TruCluster Server license PAK.

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 and repair a system during an emergency.

Load only the TruCluster Server license at this time. Do not load the Tru64 UNIX license PAK. (You will load the Tru64 UNIX license PAK and any other license PAKs you need after you boot the new member for the first time.)

The clu_add_member command writes a log file of the installation to /cluster/admin/clu_add_member.log. Examine this log file for errors before continuing. (Section D.2 contains a sample clu_add_member log file.)

Note

As described in Section 3.7.2, the clu_add_member command attempts to provide some hints about the physical location of a new member's boot disk. This information is displayed on the screen and written to the clu_add_member.log file.

5.4    Boot the New Member

After running clu_add_member, go to the console of the newly installed member and perform the following steps:

  1. At the console of the new member, set the console variable boot_osflags to A so the system will boot to multiuser mode: 

    >>> set boot_osflags A
 

  2. At the console of the new member, boot genvmunix from the new member's boot disk: 

    >>> boot -file genvmunix new_member_boot_disk
 

    Remember to specify the correct DK device name for the boot disk at the console; do not use the dsk special file name you supplied to clu_add_member. For example, if the console device name for the new member's boot disk is DKC600: 

    >>> boot -file genvmunix DKC600
 

    Caution

    If you are not sure of the location of the newly installed boot disk, use the information in Section 3.7.2 to determine its physical location.

    In addition to making sure you boot the correct disk, note that you cannot copy a member's boot disk to another disk and then boot that member from the copy. You must boot a member from the disk created by clu_add_member. To change the boot disk for a member, you must reinstall the member following the instructions in Section 6.2.

  3. During its first boot, the new member automatically performs the following tasks:

    1. Configures all loaded subsets.

    2. Attempts to build a customized kernel.

      • If the kernel build succeeds, copies the new kernel to the member's boot partition.

      • If the build does not succeed, when the system reaches multi-user mode, you can run doconfig to build a kernel. Copy (cp) the new kernel from /sys/HOSTNAME/vmunix to /vmunix. (If you move (mv) the kernel to /vmumix, you will overwrite the /vmunix CDSL.)

    3. Runs a script so you can configure additional network interfaces. (The clu_add_member command configures only the cluster interconnect interface.) We recommend that you configure at least one additional interface: the public network interface that is associated with the new member's host name.

      Note

      If there is no interface associated with the new member's host name and if you use the Common Desktop Environment (CDE), CDE will display an error dialog box when you first log in. Read the dialog box, then click on OK to log out. Select a failsafe session and log in again. Configure a network interface and associate it with the system's host name.

    4. Sets the boot_reset and bootdef_dev variables, and creates and sets the boot_dev console variable.

  4. The system continues to boot to multi-user mode. When the system finishes booting to multiuser mode, register the Tru64 UNIX license and any other required application licenses. If you did not register the TruCluster Server license while running clu_add_member, register it now.

  5. Because this member is still running genvmunix, reboot the system so it is using its custom kernel. This reboot is a required step when adding a member to the cluster. 

    # shutdown -r now
 

    Note

    If the new member's boot disk is accessed through HS controllers that are connected to dual SCSI or Fibre Channel buses and configured for multiple-bus failover, or the system is an AlphaServer 8200 or 8400, halt the system and see Section 2.7 for information on setting the bootdef_dev console variable.

When first booted as a cluster member, the system runs the clu_check_config command to examine the configuration of several important cluster subsystems. Look at the clu_check_config log files in the /cluster/admin directory to verify that these subsystems are configured properly and operating correctly. If you discover any problems, read clu_check_config(8) so you know what tests the command performs. You can then run the command in verbose mode to display more information about why a subsystem failed the initial test. See the Tru64 UNIX System Administration and the TruCluster Server Cluster Administration manuals for information on configuring subsystems.

5.5    Make On-Disk Backup Copies of Important Configuration Files

Because cluster members rely on the information in the following files, we recommend that, after booting each additional member of the cluster, you make on-disk copies of these files in case of inadvertent modification. For member-specific files, the examples use member 2 (memberid=2). Substitute the correct member ID for your new member when making backup copies of files.