How to Use JumpStart to Install the Solaris Operating Environment and Establish New Cluster Nodes (Sun Cluster 3.0 Installation Guide)

Sun Cluster 3.0 Installation Guide

How to Use JumpStart to Install the Solaris Operating Environment and Establish New Cluster Nodes

Perform this procedure to use the custom JumpStart installation method. This method installs the Solaris operating environment and Sun Cluster software on all cluster nodes in a single operation.

Ensure that the hardware setup is complete and connections are verified before installing Solaris software.

Refer to Sun Cluster 3.0 Hardware Guide and your server and storage device documentation for details on setting up the hardware.

On each node of the cluster, determine whether the local-mac-address variable is correctly set to false.
# /usr/sbin/eeprom local-mac-address?
- If the command returns local-mac-address=false, the variable setting is correct. Proceed to Step 3.
- If the command returns local-mac-address=true, change the setting to false.
  # /usr/sbin/eeprom local-mac-address?=false
  The new setting becomes effective at the next system reboot.

Have available the following information.
- The Ethernet address of each cluster node
- The following completed configuration planning worksheets from Sun Cluster 3.0 Release Notes.
  - "Local File System Layout Worksheet"
  - "Cluster and Node Names Worksheet"
  - "Cluster Interconnect Worksheet"
See Chapter 1, Planning the Sun Cluster Configuration for planning guidelines.

Update naming services.

Add address-to-name mappings for all public hostnames and logical addresses, as well as the IP address and hostname of the JumpStart server, to any naming services (such as NIS, NIS+, or DNS) used by clients for access to cluster services. See "IP Addresses" for planning guidelines. You also add these addresses to the local /etc/inet/hosts file on each node during the procedure "How to Configure the Name Service Switch".

Note -
If you do not use a name service, create jumpstart-dir/autoscinstall.d/nodes/nodename/archive/etc/inet/hosts files on the JumpStart install server, one file for each node of the cluster, where nodename is the name of a node of the cluster. Add the address-to-name mappings there.

As superuser, set up the JumpStart install server for Solaris operating environment installation.

Refer to the setup_install_server(1M) and add_install_client(1M) man pages and Solaris Advanced Installation Guide for instructions on setting up a JumpStart install server.

When setting up the install server, ensure that the following requirements are met.
- The install server is on the same subnet as the cluster nodes, but is not itself a cluster node.
- The install server installs the release of the Solaris operating environment required by the Sun Cluster software.
- A custom JumpStart directory exists for JumpStart installation of Sun Cluster. This jumpstart-dir directory must contain a copy of the check(1M) utility and be NFS exported for reading by the JumpStart install server.
- Each new cluster node is configured as a custom JumpStart install client using the custom JumpStart directory set up for Sun Cluster installation.

(Optional) Create a directory on the JumpStart install server to hold your copies of the Sun Cluster and Sun Cluster data services CD-ROMs.

In the following example, the /export/suncluster directory is created for this purpose.
# mkdir -m 755 /export/suncluster

Copy the Sun Cluster CD-ROM to the JumpStart install server.
1. Insert the Sun Cluster 3.0 CD-ROM into the CD-ROM drive on the JumpStart install server.
  
  If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/suncluster_3_0 directory.
2. Change to the /cdrom_image/suncluster_3_0/SunCluster_3.0/Tools directory.
  # cd /cdrom_image/suncluster_3_0/SunCluster_3.0/Tools
3. Copy the CD-ROM to a new directory on the JumpStart install server.
  
  The scinstall command creates the new install directory as it copies the CD-ROM files. The install directory name /export/suncluster/sc30 is used here as an example.
  # ./scinstall -a /export/suncluster/sc30
4. Eject the CD-ROM.
  # cd / # eject cdrom
5. Ensure that the Sun Cluster 3.0 CD-ROM image on the JumpStart install server is NFS exported for reading by the JumpStart install server.
  
  Refer to NFS Administration Guide and the share(1M) and dfstab(4) man pages for more information about automatic file sharing.

From the JumpStart install server, start the scinstall(1M) utility.

The path /export/suncluster/sc30 is used here as an example of the install directory you created.
# cd /export/suncluster/sc30/SunCluster_3.0/Tools # ./scinstall
Follow these guidelines while using the interactive scinstall utility.
- Interactive scinstall enables you to type ahead. Therefore, do not press Return more than once if the next menu screen does not appear immediately.
- Unless otherwise noted, pressing Control-D returns you either to the start of a series of related questions or to the Main Menu.
- Your session answers are stored as defaults for the next time you run this menu option.

To choose JumpStart installation, type 3 (Configure a cluster to be JumpStarted from this install server).

Note -
If option 3 does not have an asterisk in front, this omission indicates the option is disabled because JumpStart setup is not complete or has an error. Exit the scinstall utility, correct JumpStart setup, then restart the scinstall utility.

Follow the prompts to specify Sun Cluster configuration information.
- JumpStart directory name
- Cluster name
- Cluster node names
- Node authentication
- Private network address and netmask--You cannot change the private network address after the cluster has successfully formed
- Cluster interconnect (transport adapters and transport junctions)--You can configure no more than two adapters by using the scinstall command, but you can configure additional adapters later by using the scsetup utility
- Global devices file-system name
- Automatic reboot--Do not choose automatic reboot if you have Sun Cluster software patches to install
When finished, the scinstall commands generated from your input are displayed for confirmation. If you choose not to accept one of them, the scinstall utility returns you to the Main Menu. From there you can rerun menu option 3 and provide different answers. Your previous entries are displayed as the defaults.

If necessary, make adjustments to the default class file, or profile, created by scinstall.

The scinstall command creates the following autoscinstall.class default class file in the jumpstart-dir/autoscinstall.d/3.0 directory.

install_type    initial_install
system_type     standalone
partitioning    explicit
filesys         rootdisk.s0 free /
filesys         rootdisk.s1 750 swap
filesys         rootdisk.s3 100  /globaldevices
filesys         rootdisk.s7 10
cluster         SUNWCuser       add
package         SUNWman         add

Note -

The default class file installs the End User System Support software group (SUNWCuser) of Solaris software. For Sun Enterprise E10000 servers, you must install the Entire Distribution + OEM software group. Also, some third-party software, such as Oracle, might require additional Solaris packages. Refer to third-party documentation for any Solaris software requirements.

You can change the profile in one of the following ways.

Edit the autoscinstall.class file directly. These changes are applied to all nodes in all clusters that use this custom JumpStart directory.
Update the rules file to point to other profiles, then run the check utility to validate the rules file.

As long as minimum file-system allocation requirements are met, no restrictions are imposed on changes to the Solaris operating environment install profile. Refer to "System Disk Partitions" for partitioning guidelines and requirements to support Sun Cluster 3.0 software.

Are you installing a new node to an existing cluster?
- If no, proceed to Step 12.
- If yes, perform the following steps to create a mount point on the new node for each cluster file system in the cluster.
1. From another, active node of the cluster, display the names of all cluster file systems.
  % mount | grep global | egrep -v node@ | awk `{print $1}'
2. On the node you are adding to the cluster, create a mount point for each cluster file system in the cluster.
  % mkdir -p mountpoint
  For example, if a file system name returned by the mount command is /global/dg-schost-1, run mkdir -p /global/dg-schost-1 on the node being added to the cluster.

Set up Solaris patch directories.
1. Create jumpstart-dir/autoscinstall.d/nodes/nodename/patches directories on the JumpStart install server, one directory for each node in the cluster, where nodename is the name of a cluster node.
  # mkdir jumpstart-dir/autoscinstall.d/nodes/nodename/patches
2. Place copies of any Solaris patches into each of these directories. Also place copies of any hardware-related patches that must be installed after Solaris software is installed into each of these directories.

If you do not use a name service, set up files to contain the necessary hostname information.
1. On the JumpStart install server, create files named jumpstart-dir/autoscinstall.d/nodes/nodename/archive/etc/inet/hosts.
  
  Create one file for each node, where nodename is the name of a cluster node.
2. Add the following entries into each file.
  - IP address and hostname of the NFS server that holds a copy of the Sun Cluster CD-ROM image. This could be the JumpStart install server or another machine.
  - IP address and hostname of each node in the cluster.

(Optional) Add your own post-installation finish script.

You can add your own finish script, which is run after the standard finish script installed by the scinstall command.
1. Name your finish script finish.
2. Copy your finish script to the jumpstart-dir/autoscinstall.d/nodes/nodename directory, one directory for each node in the cluster.

If you are using an administrative console, display a console screen for each node in the cluster.

If cconsole(1M) is installed and configured on your administrative console, you can use it to display the individual console screens. Otherwise, you must connect to the consoles of each node individually.

From the ok PROM prompt on the console of each node, type the boot net - install command to begin the network JumpStart installation of each node.

Note -
The dash (-) in the command must be surrounded by a space on each side.
ok boot net - install
Note -
Unless you have installed your own ntp.conf file in the /etc/inet directory, the scinstall command installs a default ntp.conf file for you. Because the default file is shipped with references to eight nodes, the xntpd(1M) daemon might issue error messages regarding some of these references at boot time. You can safely ignore these messages. See "How to Update Network Time Protocol (NTP)" for information on how to suppress these messages under otherwise normal cluster conditions.

When the installation is successfully completed, each node is fully installed as a new cluster node.

Note -
The Solaris interface groups feature is disabled by default during Solaris software installation. Interface groups are not supported in a Sun Cluster configuration and should not be enabled. Refer to the ifconfig(1M) man page for more information about Solaris interface groups.

Install any Sun Cluster software patches.

Refer to Sun Cluster 3.0 Release Notes for the location of patches and installation instructions.

If you installed Sun Cluster software patches, shut down the cluster, then reboot each node in the cluster.

Before rebooting the first node of the cluster, shut down the cluster by using the scshutdown command. Until the cluster nodes are removed from install mode, only the first node, which establishes the cluster (the sponsor node), has a quorum vote. In an established cluster which is still in install mode, if the cluster is not shut down before the first node is rebooted, the remaining cluster nodes cannot obtain quorum and the entire cluster shuts down.

Cluster nodes remain in install mode until the first time you run the scsetup(1M) command, during the procedure "How to Perform Post-Installation Setup".

Where to Go From Here

To set up the name service look-up order, go to "How to Configure the Name Service Switch".