Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next

Generating the Foundation Services and Solaris Configuration Files

This section describes how to generate the Foundation Services and Solaris operating system configuration files for the cluster by using the sldeploy command.

The sldeploy command does the following:

  • Generates the Foundation Services configuration files.

    The Foundation Services configuration files include the nhfs.conf file. The Foundation Services configuration files are generated from the cluster configuration files cluster.conf, machine.conf, and network.conf.

  • Generates the Solaris operating system configuration files.

ProcedureTo Generate the Foundation Services and Solaris Configuration Files by Using the sldeploy Command

  1. Log in to the build server.

  2. Run the sldeploy command:

    $ sldeploy -n SWL1 -v ha_v1

The sldeploy command is run once for each software load because all node groups are processed in one operation.

For more information on the sldeploy command, see the sldeploy(1M) man page.

Copying the Foundation Services and Solaris Configuration Files to an Export Directory

Use the slexport command to copy the generated Foundation Services and Solaris operating system configuration files created by sldeploy, into the export directory. The export directory is used by the fldeploy command to generate a deployable flash archive and associated Solaris JumpStart environment.

ProcedureTo Copy the Generated Foundation Services and Solaris Configuration Files to the Export Directory by Using the slexport Command

  1. Log in to the build server.

  2. Run the command slexport:

    $ slexport -n SWL1 -v ha_v1

    This command exports the generated Foundation Services and Solaris operating system configuration files in SWL1, to the directory SMCT_EXPORT_DIR/SWL1@ha_v1.

The slexport command copies the software load data to the export directory, including data previously generated by the slcreate and slconfig commands.

For information, see the slexport(1M) man page.

Modifying the Installation Server Configuration File

This section describes how to configure the installation server configuration file, install-server.conf, so that the Solaris JumpStart environment can be created by the fldeploy command.

ProcedureTo Enable Solaris JumpStart Environment Creation by Configuring the Installation Server Configuration File

  1. Log in to the installation server.

  2. Modify the install-server.conf file to include the cluster addressing schema.

    The install-server.conf file must contain the same network address and same netmask as the target cluster. It must also include an IP address that is not used by the cluster nodes.

    A template for the install-server.conf file is provided in the /opt/SUNWcgha/nhsmct/etc/models directory on the build server.

    For information, see the install-server.conf(4) man page.

Customizing the Solaris JumpStart Files for a Target Cluster

Solaris JumpStart files are required by the master-eligible nodes and dataless nodes. The system identification configuration file contains information for the target cluster such as name service, timezone and superuser password. Templates for the target cluster are provided in the /opt/SUNWcgha/nhsmct/etc/jumpstart directory. These templates contain the .cluster extension.

Note that the Foundation Services default superuser password is sunrules.

ProcedureTo Configure the Solaris JumpStart System Identification File

  1. Copy the sysidcfg.proto template from the /opt/SUNWcgha/nhsmct/etc/jumpstart/ directory to one of the following directories:

    • smct-dir/jumpstart/

    • user-config-dir/jumpstart/

  2. Modify the file sysidcfg.cluster to suit your local environment.

    You can configure the following parameters:

    • system_locale

    • timezone

    • terminal

    • root_password

    • monitor

    • keyboard

    • display

    • pointer


Note - Although the template files for the proto.cluster, rules.cluster and finish.cluster files are provided, do not configure them. The template for the begin.cluster file is supported by the SMCT. Modify this file if required. For more information, see the Solaris JumpStart documentation.


Previous Previous     Contents     Index     Next Next