Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next

For information on the syntax used in the machine.conf file, see the machine.conf(4) man page.

For examples of file system definition sections of the machine.conf file, see Appendix B, Configuration File Examples for the machine.conf File.

Configuring the network.conf File

You must configure the network.conf file in stage 1 if you have:

  • Configured the network interfaces in the machine.conf file in stage 1

  • Configured a domain that defines IP, router or network information in the cluster.conf file

If you did not configure network interfaces in the machine.conf or cluster.conf files, you can configure the network.conf file in stage 3. For more information, see Adding Cluster-Specific Configuration Data to the network.conf File.

For more information, see the network.conf(4) man page.

Creating a Software Configuration File for a Node Group

A software configuration file is an optional file that defines software for installation on a specific node group in addition to the Foundation Services and Solaris operating system.

ProcedureTo Create a Software Configuration File

  1. Create a software configuration file for each node group that requires additional software packages or software patches.

    For more information on software configuration files, including examples, see the software.conf(4) man page.

A software configuration file is used as a parameter of the slcreate command. For more information, see the slcreate(1M) man page.

Customizing Solaris JumpStart Files for the Prototype Machine

Solaris JumpStart files are required by the master-eligible node groups and dataless node groups. At this stage, you have the option to customize the Solaris JumpStart files for the prototype machine.

If you do not want to customize the Solaris JumpStart files for the prototype machine, skip this section. To customize the Solaris JumpStart files, you can do the following:

  • Add additional Solaris packages from the Solaris distribution installed on the installation server

  • Adapt to the target cluster environment, for example choice of language, timezone

  • Change the default superuser password

Templates for Solaris JumpStart files for the prototype machine are provided in /opt/SUNWcgha/nhsmct/etc/jumpstart, and contain the .proto extension:

  • profile.proto

  • begin.proto

  • sysidcfg.proto

Do not modify the rules.proto or finish.proto files.

For information about changing parameters in Solaris JumpStart files, see the Solaris JumpStart documentation.

ProcedureTo Configure the Solaris JumpStart profile File for the Prototype Machine

Each profile file defines the set of Solaris operating system packages to be installed on each master-eligible node and dataless node.

A template for the profile file, named profile.proto, is provided in /opt/SUNWcgha/nhsmct/etc/jumpstart/Solaris_version.

  1. Log in to the build server.

  2. Copy the profile.proto template from /opt/SUNWcgha/nhsmct/etc/jumpstart/Solaris_version to one of the following directories:

    • smct-config-dir/jumpstart/Solaris_version

    • user-config-dir/jumpstart/Solaris_version

    Each profile file must be named in the following format:

    profile.target[.extension]

    Where:

    • target is .proto for the prototype machine

    • extension is the name of the master-eligible or dataless node group as defined in the cluster.conf file

    For example, a Solaris JumpStart profile file for the node group soft_switch is profile.proto.soft_switch.

  3. Modify the following parameters:

    • geo

      This must be set to your geographical location. For example, W_Europe.

    • locale

      This must be set to your required language. For example, en_US.

  4. (Optional) Modify the following parameters:

    • cluster

      This must include the default value SUNWcreq

    • package

      The list of Solaris operating system packages to be installed on each master-eligible node or dataless node. You can add to the list of packages but do not delete any packages already defined in the template.

  5. Do not configure the following parameters:

    • backup_media

    • client_arch

    • client_root

    • client_swap

    • fdisk

    • isa_bits

    • boot_device

      This is managed by the SMCT

    • root_device

      This is managed by the SMCT

    • use_disk

      This is managed by the SMCT

    • filesys

      This is managed by the SMCT

    • dontuse

    • layout_constraint

    • num_clients

  6. Do not modify the following parameters:

    • install_type

    • system_type

    • partitioning

Previous Previous     Contents     Index     Next Next