 |
Index for
Section 8 |
|
 |
Alphabetical
listing for C |
|
 |
Bottom of
page |
|
clu_create(8)
NAME
clu_create - Create a cluster
SYNOPSIS
/usr/sbin/clu_create [-c member_conf_file]
FLAGS
-c member_conf_file
When invoked with the -c flag, clu_create runs in non-interactive
mode, taking its input from the specified configuration file.
DESCRIPTION
The clu_create command creates a cluster. 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 online help. To display a help message, type the word
help or a question mark, ?, at any prompt. The command also writes a log
file, /cluster/admin/clu_create.log.
The first time clu_create is run, it creates a configuration file in
/cluster/admin/.membern.cfg; for example, .member1.cfg. This configuration
file contains a list of variable=value pairs. Each time clu_create is run,
it appends the latest configuration data to this file in the /cluster/admin
directory.
When invoked with the -c flag, clu_create runs in non-interactive mode,
taking its input from a configuration file. If clu_create -c encounters a
fatal error, it exits. In addition, no interactive options are presented.
For example, clu_create -c does not offer to reboot the system; you must
perform a manual reboot after the command completes.
The following is an example of a clu_create configuration file for a
cluster that has installed the Worldwide Language Support subsets and uses
LAN hardware for its cluster interconnect:
# clu_create saved configuration values:
# date: Mon Jan 22 17:13:47 EST 2001 hostname pepicelli.zk3.dec.com
# Previously saved value in this file have been \
# converted to comment lines
clu_alias_ip=16.140.112.209
clu_boot_dev=dsk10
clu_i18n_dev=dsk14
clu_ics_dev=ics0
clu_ics_host=pepicelli-ics0
clu_ics_ip=10.0.0.1
clu_mem_votes=1
clu_memid=1
clu_name=deli.zk3.dec.com
clu_nr_dev=nr0
clu_phys_devs=ee0,ee1
clu_quorum_dev=dsk7
clu_quorum_votes=1
clu_root_dev=dsk1b
clu_tcp_host=member1-icstcp0
clu_tcp_ip=10.1.0.1
clu_usr_dev=dsk2c
clu_var_dev=dsk3c
A configuration file makes it easy to re-create an existing single-member
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_create -c on the same system it was run on
previously and that the storage configuration has not changed. (The date:
comment line in the configuration file contains the date that clu_create
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_create -c after booting the operating system on
which you created the cluster:
# /usr/sbin/clu_create -c /cluster/admin/.member1.cfg
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 and
creating a cluster. Refer to these manuals before running the clu_create
command.
The following list outlines the steps needed to create a new 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. Selecting AdvFS file systems, install the base operating system on the
system that will become the first cluster member. The disk or disks
used for the base installation can either be private to this system or
on a shared bus that the system can access.
Note
You install the base 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 base operating 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 software. (After you load the
cluster license and software, you can install a patch kit and patch
both the base and cluster software before creating a cluster.)
5. After completing the checklists in the TruCluster Server Cluster
Installation manual, run the clu_create command to create a boot disk
for the first cluster member and to create and populate the
clusterwide root (/), /usr, and /var AdvFS file systems.
6. Halt the 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.
FILES
/usr/sbin/clu_create
Specifies the command path.
/cluster/admin/clu_create.log
Log file for clu_create.
/cluster/admin/.membern.cfg
Configuration file created by clu_create.
RELATED INFORMATION
Commands: clu_add_member(8), clu_check_config(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 |
|