Solaris 2.8: Installation Using JUMPSTART

This document describes how to completely setup and install a NEW Sun workstation using JUMPSTART.

****************

Standalone. The host has one or more internal disks (at least 1 GB). The disk(s) contains the root partition, the swap partition, the /usr partition, the /opt partition, the /usr/local partition, and the /usr/openwin partition. It obtains /var/mail from the server via NFS.

Homeserver. The host has one or more internal disks (at least 1 GB). The disk(s) contains the root partition, the swap partition, possibly a /var partition, possibly a /var/mail partition, the /usr partition, the /opt partition, the /usr/local partition, and the /usr/openwin partition. The only partition it mounts from the server is the /var/mail par tition; some systems in this configuration do not even do that, and store mail locally. A homeserver contains /export/home partitions on one or more disks.

****************

The 2.8 installation on a new machine is best performed after the igor and registration has been propagated. Igor entries can be hand editted, but the registration must be complete. An unattended installation (after the initial boot) requires that the new machine be on the same subnet as the "jumpstart" machine. The required steps include: registration, igor entry, jumpstart setup and network software installation, manual rdist, and followup acmaint and egad entries.

If the new machine replaces an existing machine: You must first run savefiles on the existing machine:

from harbor as root, type: rsh host-being-upgraded "cd /home/harbor/system/solsave/bin; ./savefiles-os.sh"

(This saves files and setting such as acmaint hostkey, calendar files, etc. Look at the savefiles script for complete details).

Set up the igor configuration files for the host you are installing a day before performing the installation:

Log in to harbor as root.

Change directories to /usr/share/adm/igor/hosts.
Checkout the appropriate server file, add a new definition for the host, then check it back in:

# co -l filename
# vi filename
# ci -u filename

The definition should look something like this, using anchor as an example:

@if HOSTNAME == "anchor"
@ define STANDALONE
@ define SITE "ecnsite"
@ define SITEBIN "ecn"
@ define NTPHOST
@ define SYSLOGHOST "pier"
@ define ACMAINT3
@ define CDE
@ define OPENGL
@ define USECACHEFS
@endif

(Note that there are many possible options in IGOR. Let the software staff make additional changes as necessary)

harbor is the Solaris 8 rdist master, and contains the default jumpstart directories. These can be copied to almost any machine to act as a jumpstart server.

cd to /var/local/install_8/clients/bin

list = the list of machines to do now; barracuda is used in these examples:

barracuda 8:0:20:xx:xx harbor 128.46.154.1 sun4u homeserver upgrade adm5
(see definitions in list )

run ./list.sh

cd back to clients, cd to barracuda.ecn.purdue.edu

edit client profile for disk configuration
/var/local/install_8/clients/barracuda.ecn.purdue.edu/barracuda

run ./check

**
to start over, run /var/local/install_8/clients/bin/rm_client barracuda
remove /var/local/install_8/clients/barracuda.ecn.purdue.edu

if barracuda previously existed in /etc/ethers, remove it before starting, or
start over after the complaint.
**

from machine being installed: boot net - install
you may have to answer the first initial  questions concerning terminal and date if a dumb terminal is used.

The default software will be installed, followed by an automatic reboot of the machine. A post-install script will run igor and install all up to date patches.  While patches are being run, run the manual rdist. From harbor, first log into the new machine as root to allow an exchange of ssh keys, otherwise  the rdist will fail.

NOTE: For convenience, a new machine can be jumpstarted from harbor on the .154 subnet, in the shop, even if the machine is to reside on another subnet. Use a temporary .154 name, and halt the machine after the initail automatice reboot. Boot single user, make sure the ogor entry exists, and the change the hostname.*, nodename, and default router to the appropriate name and subnet. Reboot the machine at the final location on the correct subnet andmonce the patches start running, proceed with the rdist.

Setting up RDIST

Set up the master rdist files for the host you are installing, on harbor as root: Change directories to /var/rdist/hosts.

Checkout the "site'' file for the appropriate site out of RCS:

# co -l "site"

Edit the file, add the host to the proper opsys/model list

Where the choices for opsys/model are "SUN_OS58_STANDALONE,'' or "SUN_OS58_HOMESERVER.''

Please preserve alphabetical order, if it exists.

Check the file back in to RCS:

# ci -u "site"

from harbor as root:

Make a distfile by issuing the following:

# /var/rdist/bin/make-distfile sun_os58_master > /tmp/Distfile.<newhostname>

This is an empty distfile. Insert host name into SUN_OS58_<model> as the only entry by using vi on the now existing /tmp/Distfile.newhostname. (example: SUN_OS58_STANDALONE ( ecnipc )

THEN RUN RDIST TO THIS HOST FROM HARBOR

Type:

# /usr/local/etc/rdist -o numchkowner,numchkgroup -f /tmp/Distfile.<hostname> > /tmp/rdist.out 2>&1 &

check the logfile ( tail -f /tmp/rdist.out on harbor) to make sure things are running.
(if the rdist aborts with a permission denied message, chmod 755 /usr/local/etc/rdistd on the machine being installed)
This will run for approx 1 hour.

Add the host to ACMAINT by following the instructions in the ACMAINT 3.0 Guide for DSM. Note that mailservers require an IGOR entry.

Send mail or contact the site specialist requesting user account installation.

When the installation is complete, and before delivering a machine, be sure to change the eeprom security-mode to command and add the security-password. Install the name/label, and record the appropriate entries in the egad database.