Information for NFS and Cluster-Local Installations

If you are installing the software either on an NFS server for remote mounting or locally on each node of a multinode cluster, you need to complete this section.

Installation Method Options

Specify either rsh or cluster-tool as the method for propagating the installation to all the nodes in the cluster.

• cluster-tool - If you choose the cluster-tool option, you will be able to use one of the Cluster Console Manager (CCM) applications, cconsole, ctelnet, or crlogin, to greatly facilitate the installation of Sun HPC ClusterTools 3.0 software on all of the nodes in your cluster in parallel. See Appendix B for information about using CCM tools.

  ---

  Note -

  You can use the CCM tools to install on up to 16 nodes at a time. For clusters with more than 16 nodes, you will have to repeat the installation process on groups of up to 16 nodes at a time until you have installed the software on the entire cluster.

  ---

• rsh - If you choose the rsh method, the software will be installed serially on the cluster notes in the order in which they are listed in hpc_config. The CCM applications cannot be used to install the software in rsh mode.

Also note that this method requires that all nodes are trusted hosts--at least during the installation process.

INSTALL_METHOD="method"

Hardware Information

There are two ways to enter information in this section:

• If the cluster nodes are connected to a terminal concentrator, list each node in the following triplet format.

  NODES="hostname1/termcon_name/port_id hostname2/termcon_name/port_id ..."

In each triplet, specify the host name of a node, followed by the host name of the terminal concentrator and the port ID on the terminal concentrator to which that node is connected. Separate the triplet fields with virgules (/). Use spaces between node triplets.

• If the cluster nodes are not connected to a terminal concentrator, simply list the node host names, separated by spaces, as follows.

  NODES="hostname1 hostname2 hostname3 ..."

Every node in your Sun HPC cluster must also be in the corresponding LSF cluster. See the discussion of the lsf.cluster.clustername configuration file in the LSF Batch Administrator's Guide for information on LSF clusters.

If you will not be using the CCM tools, you can allow the installation script to derive the node list from the LSF configuration file lsf.cluster.clustername. To do this, either set the NODES variable to NULL or leave the line commented out. You must be installing from one of the nodes in the LSF cluster.

SCI Support

This section tells the script whether to install the SCI-related packages. If your cluster includes SCI, replace choice with yes; otherwise, replace it with no.

INSTALL_SCI="yes"

A yes entry causes the three SCI packages and two RSM packages to be installed in the /opt directory. A no causes the installation script to skip the SCI and RSM packages.

The SCI and RSM packages are installed locally on every node, not on an NFS server.