Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next

ProcedureTo Mount the Installation Server Directories Onto the Prototype Machine and the Cluster

As file systems may already be shared, this section provides guidelines only.

The minimum requirements for sharing files by using the NFS are as follows:

  1. Set the permissions to read and write, -o rw,anon=0, for the directory where the flash archives are generated.

    The default directory for the flash archives is SMCT_FLASH_DIR.

  2. Set the permissions to read only, -o ro,anon=0, for the directory containing the Solaris JumpStart environment.

    The default directory for the Solaris JumpStart environment is SMCT_JUMPSTART_DIR.

  3. Set the permissions to read only, -o ro,anon=0, for the directory containing the Solaris distribution.

    The default directory for the Solaris distribution is SMCT_SOL_DIR.

  4. Set the permissions to read only, -o ro,anon=0, for the directory containing the exported software load data.

    The default directory for the exported software load data is SMCT_EXPORT_DIR.

  5. Set the permissions to read only, -o ro,anon=0, for the software repository.

    The default directory for the exported software load data is SMCT_EXPORT_DIR. If you ran the slexport command with the -r option, the default directory is SMCT_SOFTREP_DIR.

  6. Set the permissions read-writer permissions, -o rw,anon=0, for the SMCT temporary directory.

    The default temporary directory is SMCT_TMP_DIR.

ProcedureTo Disable the Installation Server as a Router

  1. Disable the installation server as a router by creating a /etc/notrouter file:

    # touch /etc/notrouter

    If a system running the Solaris operating system has two network interfaces, it is configured as a router by default. However, a Foundation Services cluster network must not be routed for security reasons.

ProcedureTo Reboot the Installation Server to Start the Solaris Daemons

  1. Reboot the installation server to start or restart the Solaris daemons:

    # init 6

    The following daemons are started or are restarted:

    • rarpd

    • rpc.bootparamd

    • lockd

    • statd

    • mountd

    • nfsd

    • inetd

Configuring the Prototype Machine

This section describes how to erase a previous DHCP boot configuration on the prototype machine.

ProcedureTo Set the Boot Device on the Prototype Machine

  1. Get the ok prompt on the prototype machine.

    For example:

    telnet> send brk
    ok>

  2. Configure the OBP parameters:

    ok> setenv boot-device disk net

SMCT Configuration File Locations

The following files are the SMCT configuration files:

  • cluster.conf

  • machine.conf

  • network.conf

  • master-system.conf

  • install-server.conf

Each SMCT configuration file has a template file in the directory /opt/SUNWcgha/nhsmct/etc/models. Make sure that you have copied the template files to a directory of your choice as described in the Netra High Availability Suite Foundation Services 2.1 6/03 Release Notes.

The default directory for the cluster configuration files is the smct-config-dir/models directory. If the -c option is not used when running SMCT commands, the cluster configuration files are expected to be located in this directory.

If you copy the templates to a user-defined configuration directory, you must use this directory location with the -c option when running the SMCT commands.

When you run an SMCT command, the SMCT looks for the configuration files first in the directory specified with the -c option if used. If the -c option is not used, the SMCT looks for the necessary configuration files in the smct-config-dir. If there are no files in the smct-config-dir, the SMCT looks for the configuration files in the /opt/SUNWcgha/nhsmct/etc/models/ directory.

For information about the configurable elements of these files, see Appendix A, Configuration Element Rules.

Previous Previous     Contents     Index     Next Next