sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
2. Chapter 7 # Configuration Stage 3: Configuring the Flash Archive for Deployment This chapter describes how to configure your flash archive for a specific cluster hardware and network configuration. The flash archive can be one of the following: A generic flash archive created in stage 1, as described in Chapter 5, Configuration Stage 1: Creating a Generic Flash Archive. A configured flash archive created in stage 2, as described in Chapter 6, Configuration Stage 2: Adding User-Defined Data to the Flash Archive. Configuration stage 3 generates the Foundation Services configuration data and a Solaris JumpStart environment for each master-eligible node group and dataless node group. This configuration stage can be performed on a flash archive that has already been deployed but which requires an updated networking and cluster hardware configuration. Stage 2 can be rerun before performing stage 3. When stage 3 is complete, you have one or more deployable flash archives with a cluster-specific configuration, and, optionally, user-defined configuration data and application installation scripts. This chapter contains the following sections: Configuration Stage 3 Checklist Configuration Stage 3 Procedure Transferring Your SMCT Environment From the Build Server to the Installation Server Modifying `/etc` Files Adding Cluster-Specific Configuration Data to the `machine.conf` File Adding Cluster-Specific Configuration Data to the `network.conf` File Generating the Foundation Services and Solaris Configuration Files Copying the Foundation Services and Solaris Configuration Files to an Export Directory Modifying the Installation Server Configuration File Customizing the Solaris JumpStart Files for a Target Cluster Creating a Deployable Flash Archive and the Solaris JumpStart Environment Modifying User-Defined Configuration Data ## Configuration Stage 3 Checklist Before you perform configuration stage 3, ensure that: You have created a generic flash archive or configured flash archive as described in Chapter 5, Configuration Stage 1: Creating a Generic Flash Archive and Chapter 6, Configuration Stage 2: Adding User-Defined Data to the Flash Archive. You have connected the installation server to the master-eligible nodes and dataless nodes on the cluster. The network parameters in the `install-server.conf` file are consistent with the network parameters in the `network.conf` file. ## Configuration Stage 3 Procedure The following figure illustrates the configuration procedure for stage 3, resulting in a running cluster. Figure 7-1 Configuration Stage 3 The post-installation tasks are described in detail in Figure 6-2. ## Transferring Your SMCT Environment From the Build Server to the Installation Server This section describes how to transfer flash archives and software load data from the build server to an installation server. The build server can have either a local connection to the installation server or the installation server can be at a remote site. If you are using your build server as an installation server, you do not need to read this section. Choose one of the following ways to transfer your SMCT environment: Transfer the exported data and flash archives only This option allows you to deploy the software load using `fldeploy` only. You cannot make any changes to software load data. Transfer the complete SMCT directory This option allows you to modify the existing software load for deployment to another cluster. ### To Transfer the Exported Data and Flash Archives From the Build Server to the Installation Server Note - It is not necessary to copy the software load data or the cluster configuration files to the installation server. The `sldeploy` command has already been executed on the build server. If you follow this procedure, you cannot modify software load data or run the `slxxx` commands. To modify software load data, follow the procedure To Transfer the Complete SMCT Environment From the Build Server to the Installation Server. Log in to the build server. Export the software load data:
       # slexport -r -n swl-name -v swl-version -e export-dir
4. Ensure that the export-dir is NFS mounted and readable from the installation server. Copy the exported data from the build server to the installation server:
       # cp -r export-dir install-server-dir
5. On the installation server, copy the flash archives from the build server:
       # cp mounted_dir/flash_archive1 SMCT_FLASH_DIR
6. On the installation server, run the `nhsmctsetup` command:
       # /opt/SUNWcgha/nhsmct/bin/nhsmctsetup -w working-dir -s solaris-dist
Where working-dir specifies the root directory of the SMCT environment that is to be created. This command enables you to run the `flxxx` commands on the installation server. For more information, see the `nhsmctsetup`(1M) man page. Run the `fldeploy` command. The `fldeploy` command uses the exported data copied from the build server. For information on how to run the `fldeploy` command, see To Create a Deployable Flash Archive and the Solaris JumpStart Environment by Using the `fldeploy` Command.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems