 |
Index for
Section 8 |
|
 |
Alphabetical
listing for C |
|
 |
Bottom of
page |
|
clu_add_member(8)
NAME
clu_add_member - Add a member to a cluster
SYNOPSIS
/usr/sbin/clu_add_member [-c member_conf_file]
FLAGS
-c member_conf_file
When invoked with the -c flag, clu_add_member runs in non-
interactive mode, taking its input from the specified
configuration file.
DESCRIPTION
The clu_add_member command adds a member to an existing cluster. It
configures the cluster for a new member and creates a boot disk for that
new member. You must be root to run this command.
When run without the -c flag, the command is interactive. It prompts for
the information required to perform each task, displays the entered
information so you can check its accuracy, and, only after you confirm that
the information is correct, modifies the system. The command provides also
online help. To display a help message, type the word help or a question
mark, ?, at any prompt.
When invoked with the -c flag, clu_add_member runs in non-interactive mode,
taking its input from a configuration file. If clu_add_member -c
encounters a fatal error, it exits. In addition, no interactive options are
presented.
The following is an example of a clu_add_member configuration file created
when adding a member to a cluster that uses LAN hardware for its cluster
interconnect:
# clu_add_member saved configuration values
# date: Mon Jan 22 17:46:48 EST 2001 hostname pepicelli.zk3.dec.com
# Previously saved value in this file have been \
# converted to comment lines
clu_boot_dev=dsk12
clu_ics_dev=ics0
clu_ics_host=polishham-ics0
clu_ics_ip=10.0.0.2
clu_license=''
clu_mem_votes=1
clu_memid=2
clu_nr_dev=nr0
clu_phys_devs=ee0,ee1
clu_tcp_host=member2-icstcp0
clu_tcp_ip=10.1.0.2
unix_dev=''
unix_host=polishham.zk3.dec.com
unix_ip=''
(If present, clu_add_member uses the values for unix_dev (a network device
such as tu0), unix_ip (an IP address), and unix_host to configure the
network interface associated with the hostname of the new member.)
A configuration file makes it easy to re-add a member to cluster. However,
the information in the configuration file must be accurate; for example,
host names, IP addresses, and disk dsk names. Because disk devices are
named in order of discovery, using a configuration file implies that you
run clu_add_member -c on the same system it was run on previously and that
the storage configuration has not changed.
When using configuration files, add the members in the same order used when
creating the original cluster. For each member, run clu_add_member on the
same member it was run on previously. (The date: comment line in the
configuration file contains the date that clu_add_member was run and the
name of the host on which it was run.)
Both clu_create and clu_add_member write configuration files to the
/cluster/admin directory. Because there is no way to discern the type of
file from the .membern.cfg file name, look at the comments to determine
whether clu_create or clu_add_member created the file.
The configuration files are generated by programs and read by programs. In
general, do not manually edit configuration files. The following example
shows how you might use clu_add_member -c to re-add two members to a
cluster. Remember that the storage configuration must be the same as when
the members were last added, that a member must be added from the same
member as last time, and that you must boot each member before adding the
next:
# /usr/sbin/clu_add_member -c /cluster/admin/.member2.cfg
[Boot the second member. Determine which member added the
third member (look at the date: lines in the configuration
files). Add the third member.]
# /usr/sbin/clu_add_member -c /cluster/admin/.member3.cfg
[Boot the third member.]
The TruCluster Server Cluster Hardware Configuration manual describes how
to set up and configure the processors, interconnects, and storage for a
cluster. The TruCluster Server Cluster Installation manual provides
detailed information on installing the TruCluster Server software, creating
a cluster, and adding members. Refer to these manuals before running the
clu_add_member command.
The following list outlines the steps needed to add a new member to a
TruCluster Server cluster (see the TruCluster Server Cluster Installation
manual for full instructions):
1. Using the information in the TruCluster Server Cluster Hardware
Configuration manual, configure system and storage hardware and
firmware.
2. Read the appropriate chapters in the TruCluster Server Cluster
Installation manual and fill in the checklists provided there.
3. Bring the new system to the console level. Set the following console
variables:
>>> set bus_probe_algorithm new
>>> set boot_reset on
>>> set auto_action halt
>>> set bootdef_dev ""
4. On a current cluster member, run the clu_add_member command. The
command prompts for the information needed to add a member to the
cluster, 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. (You do not need to load
the PAK at this time, but you will need to load both the TruCluster
Server license PAK and the base operating system license PAK after you
boot the new system.)
The clu_add_member command writes a record of the session to a log
file, /cluster/admin/clu_add_member.log. It also writes the new
member's configuration information to /cluster/admin/.membern.cfg,
where n is the member ID of the new member.
5. When clu_add_member completes, go to the console of the newly
installed member, set boot_osflags to A, and boot genvmunix from the
new member's boot disk. Make sure to boot the disk you just configured
for this member. For example, if you entered dsk12 for the boot disk
in clu_add_member and you know that dsk12 is DKC600 from the new
system's console:
>>> set boot_osflags A
>>> boot -file genvmunix dkc600
6. The clu_add_member commands puts several it(8) files on the new
member's boot partition. When first booted, the new member
automatically performs the following tasks:
· Configures all loaded subsets.
· Attempts to build a customized kernel.
· If the kernel build succeeds, copies the new kernel to the
member's boot partition.
· 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 interface that is associated with
the new member's host name.
· Sets the boot_reset, bootdef_dev, and boot_dev console variables.
7. The system continues to boot to multi-user mode. Log in as root and
register the base operating system license and any other required
application licenses. If you did not register the TruCluster Server
license while running clu_add_member, register it now.
8. 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 a cluster.
# shutdown -r now
FILES
/usr/sbin/clu_add_member
Specifies the command path.
/cluster/admin/clu_add_member.log
Log file for clu_add_member.
/cluster/admin/.membern.cfg
Configuration file created by clu_add_member.
RELATED INFORMATION
Commands: clu_check_config(8), clu_create(8), clu_delete_member(8),
clu_upgrade(8)
TruCluster Server Cluster Hardware Configuration
TruCluster Server Cluster Installation
|
Index for
Section 8 |
|
|
Alphabetical
listing for C |
|
 |
Top of
page |
|