Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next
Chapter 5

Configuration Stage 1: Creating a Generic Flash Archive

This chapter describes stage 1 of the configuration process. It describes how to complete the cluster configuration files, software configuration files, and the configuration files for Solaris JumpStart.

This section describes how to create the cluster configuration files cluster.conf, machine.conf, and network.conf. If you are using an example hardware configuration, you can use the templates of the cluster configuration files provided with the product. For the example hardware configuration templates, see Templates for Example Hardware Configurations. Although template files are provided for the example hardware configurations, you may still need to make some modifications. When all the configuration files have been created, create a software load. In addition, create the Solaris JumpStart environment for the prototype machine. Then, you have to boot the prototype machine with the node group software.

When the node group software has been installed on the prototype machine, a generic flash archive is created on the build server.

When stage 1 has been completed, you have one or more generic flash archives for a generic cluster configuration.

This chapter covers the following topics:

Configuration Stage 1 Checklist

Before you perform configuration stage 1, ensure that you have:

Configuration Stage 1 Procedure

The following figure shows the configuration procedure for stage 1.

Figure 5-1 Configuration Stage 1

Diagram shows the stage 1 of the configuration process, ending with the creation of a generic flash archive on the build server

Connecting the Prototype Machine to the Build Server

Before you start configuration stage 1, make sure that you have edited the install-server.conf and master-system.conf files, as described in this section.

For information about connecting the prototype machine to the cluster, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide.

ProcedureTo Connect the Prototype Machine to the Build Server

The files described in this section are used later in the procedure by the flinstall command. For more information on flinstall, see the flinstall(1M) man page.

  1. Log in to the build server as superuser.

  2. Copy the install-server.conf file from the /opt/SUNWcgha/nhsmct/etc/models directory to your chosen destination directory, smct-config-dir/models, removing the *.tmpl extension.

    For example:

    # cp /opt/SUNWcgha/nhsmct/etc/models/install-server.conf.tmpl /
    destination_dir/install-server.conf

  3. Edit the install-server.conf file.

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

  4. Copy the master-system.conf.tmpl file from the /opt/SUNWcgha/nhsmct/etc/models directory to the smct-config-dir/models directory.

    While copying the file, remove the *.tmpl extension. For example:

    # cp /opt/SUNWcgha/nhsmct/etc/models/master-system.conf.tmpl /
    destination_dir/master-system.conf

  5. Edit the master-system.conf file with the Ethernet address configuration.

    For more information, see the master-system.conf(4) man page.

Configuring the Installation Server

This section describes how to configure the connectivity and NFS accessibility of the installation server.

ProcedureTo Configure and Activate the Network Interface That Is Connected to the Cluster

Configure and activate the network interface that is connected to the target cluster.

  1. Ensure that the interface does not conflict with the cluster addressing that is assigned during the installation procedure.

    Check that the IP address is not already in use.

  2. If there is an addressing conflict, modify the addressing schema in the master-system.conf and install-server.conf files to resolve the conflict.

ProcedureTo Modify the /etc/nsswitch.conf File

  1. Log in to the installation server as a superuser.

  2. Modify the /etc/nsswitch.conf file so that files is positioned before nis in the hosts, ethers and bootparams entries.

    For example:

    hosts: files nis 
    ethers: files nis 
    bootparams: files nis

Previous Previous     Contents     Index     Next Next