![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| |||||||||||||||||||||||
Planning the Disk Layout and File Systems for Dataless NodesThe following table provides the minimum space requirements for example disk partitions of a dataless node. Table 4-8 Example Disk Layout and File Systems for Dataless Nodes
Disk Space for Additional Diskless Nodes and Additional Node GroupsThis section describes the additional disk space you require when configuring a disk layout for additional diskless nodes or diskless node groups.
For example, to add a node group that includes two diskless nodes, you require the following disk space: 255 Mbytes + (2 * 160 Mbytes) = 575 Mbytes Creating the SMCT EnvironmentAn environment must be created for each user planning to deploy the Foundation Services by using the SMCT. Note that you must use the UNIX Korn shell when creating the SMCT environment. To create the SMCT environment, perform the following procedure on the build server. Perform this procedure on the installation server if it is the same machine as the build server.
|
# ksh /opt/SUNWcgha/nhsmct/bin/nhsmctsetup |
You are prompted to define your SMCT environment by choosing a series of environment variables. After you have entered values for these variables, they are stored in the environment definition file, smct.env.
In addition to the smct.env file, the nhsmctsetup command also creates a software repository and a software load repository.
For more information, refer to the nhsmctsetup(1M) man page.
Create an alias in your environment to the slxxx and flxxx commands.
Ensure that you are in the Korn shell and run the following command:
# . $SMCT_ENV_DIR/scripts/smct.env |
This command must be run each time you return to your SMCT environment.
For more information on SMCT environment variables, refer to the nhsmctsetup(1M) man page.
The following directories have been created on the build server:
/opt/SUNWcgha/nhsmct/etc
/opt/SUNWcgha/nhsmct/bin
/opt/SUNWcgha/nhsmct/lib
The following table describes the contents of the /opt/SUNWcgha/nhsmct/etc/ directory.
Table 4-9 SMCT Directory Contents
There are three configuration files used in the SMCT deployment process: cluster.conf, machine.conf, and network.conf.
All three configuration files must be modified to suit your deployment environment. A set of three templates for each example hardware configuration are provided with the software distribution of the Foundation Services.
For information about the example hardware configurations, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide.
For the list of templates, see the Netra High Availability Suite Foundation Services 2.1 6/03 Release Notes.
Copy the three configuration files for your example hardware configuration from the/opt/SUNWcgha/nhsmct/etc/models directory to your chosen destination directory, destination_dir.
The default directory for the cluster configuration files is SMCT_DEFAULT_CONFIG_DIR/models, where SMCT_DEFAULT_CONFIG_DIR is the SMCT environment variable defined by nhsmctsetup.
If you do not use the -c option when running the SMCT commands, the SMCT looks for the configuration files in the default directory. If you copy the templates to a destination_dir directory, you must specify this directory location with the -c option when running the SMCT commands.
For more information, see the nhsmctsetup(1M) man page.
Rename the files to remove the *N.NETRA-*.tmpl extension.
For example, if you are using the example hardware configuration for a six-node cluster:
# cp /opt/SUNWcgha/nhsmct/etc/models/cluster.conf.6N.NETRA-CT.tmpl \ destination_dir/cluster.conf # cp /opt/SUNWcgha/nhsmct/etc/models/machine.conf.6N.NETRA-CT.tmpl \ destination_dir/machine.conf # cp /opt/SUNWcgha/nhsmct/etc/models/network.conf.6N.tmpl \ destination_dir/config/model/network.conf |
If your cluster is not one of the example hardware configurations listed in the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide, you must create the three cluster configuration files. For information, see the following chapters.
![]() ![]() |