DESY HOME IT HOME Print Preview Print Window

How to install a SUN workgroup server with jumpstart



Note: Nearly all links refered from this URL are in AFS, they might be accessible outside our AFS cell for computers running AFS.

1. Introduction
2. Boot Server
3. Install Server
4. Installing a client
5. The postinstall script
6. Subdivided Subnets
7. Miscellaneous

Installing Patches

1. Introduction

Jumpstart is a SUN feature which helps to install system and site software on a workstation starting from the boot prom with an 'empty machine'.  Here's a (very) short description:


Prerequisites:

Client installation:

Now the following happens: The client to be installed broadcasts his ethernet hardware address (something like "08:00:20:c3:d7:22") on the ethernet and waits for a reply by someone on the same subnet (rarp request). A boot server (running "rarpd", use "/etc/init.d/nfs.server start " on the boot server if necessary) supplies the booting client with it's IP number. In the next step the client downloads a "miniroot-kernel" from the boot server via "tftp" (the tftpd and bootparamd need to run on the boot server). Next the client executes the miniroot-kernel and downloads further files and the Solaris-OS from the boot server, boots a Solaris session (as diskless client) and executes the Solaris-OS installation via the install server. The root disk layout and the installation profile are specified in "rules.ok " ( /afs/desy.de/products/solaris/jumpstart/rules.ok , see "Installing Solaris Software" Guide). At the end of the installation a positinstall script is put to /etc/rc3.d and the machine is rebooted. The original copy is located in /afs/desy.de/products/solaris/jumpstart/install_wgs_environment.sh ). During startup the person in front of the console is prompted for information... After getting the correct information and a couple of reboots+installations the system is up and should be working with the DESY-WGS setup.


2. Boot server

Currently NOT every newly installed SUN machine becomes boot server, it has to be done with one of the following procedures.
A prerequisite is enough disk space(~300MB). It is however important to have at least one working boot server on each ethernet - not FDDI - subnet. Ask the nameserver or send a mail to dns@desy.de with the subject "request {your subnet}" to find out a bootserver within your ethernet segment.

To install a boot server use either SALAD (as root):

Or (as root) use the script which is invoked by SALAD directly:

Using the script you can also specify the Solaris version on the command line (5.7|5.8). Technically the script does a NFS mount to the installationserver. In this way it's guaranteed that the prospective client gets the most recent hardware version from each Solaris release automatically (we provide the recent ones on our installationserver of course :-) ).

In order to be able to boot and install a client via ethernet the client must be registered in the DESY equipment database via woom.The following example demonstrates the use of woom to register new clients (you must be privileged):

Now every boot server knows about the new client (/tftpboot and /etc/ethers are linked to /afs/desy.de/... . The flags -os_version Solaris_2.8 and -hardware_type sparc_sun4? are important for woom since on discovering them woom will automagically ;-) update the /etc/ethers file and the /tftpboot directory. The command vos release -v salad.bin makes the changes visible to all boot servers (maybe you are not authorized to invoke these commands, if so, contact us). Make sure that you only type in the hostname from the ethernet interface. If there's an FDDI interface builtin and you run doom with the name refering to this interface the machine cannot boot (FDDI protocol will never fit in a boot prom). The same problem will occur if the mac address is already listed in /etc/ethers. The bootserver takes the first entry.


3. Install server

The install server supplies the client with the Solaris OS. At DESY the install server for Solaris is located on budbundy. It contains Solaris 7 and 8 OS versions. 


4. Installing a client

Make sure that you have a running boot server serving the right OS version on the same ethernet subnet (realistically you will have less trouble just starting the installation and only in case of problems look into that). Register the new client in the central registry with woom. Perform a shutdown on the client (or if it's a new machine just switch it on). The client should now prompt OK> . Type

There might be some simple questions to be answered, like timezone (DESY is in the middle of Europe, MET is appropriate), subnet mask (255.255.255.0, I think this is already proposed in the menue) and so on. At some point you are through with this (now it takes 25 seconds for me since I already know the answers now). Then the following will appear on the display telling you that the jumpstart installaion has begun. If something goes wrong up to here, don't worry, you can always easily start from scratch. The output on the console should say something like:

Checking rules.ok file...
Using begin script: scripts/say_hi.sh
Using profile: basic_install_zeus-wgs_2GB
Using finish script: scripts/zedy_jumpstart_finish_script.sh
==> BeginScript: Hi, this is your begin script for system installation
==> BeginScript: Terminated sucessfully.
Selecting cluster: SUNWCXall
š
Total software size: 271.74 MB
š
Preparing system to install Solaris. Please wait.
š
Setting up disk c0t3d0:
- Creating Solaris disk label (VTOC)
š
Creating and checking UFS file systems:
- Creating / (c0t3d0s0)
š- Creating /var (c0t3d0s3)
š- Creating /scratch (c0t3d0s4)
š- Creating /opt (c0t3d0s5)
š- Creating /usr (c0t3d0s6)
š- Creating /afscache (c0t3d0s7)
Beginning Solaris package installation...
SUNWcsu.....done. 255.89 MB remaining.
SUNWcsr.....done. 247.26 MB remaining.
SUNWcsd.....done. 247.20 MB remaining.
SUNWmfrun...done. 243.37 MB remaining.
SUNWkvma.m..done. 243.33 MB remaining.
...*

At the end of the system Installation the "finish_jumpstart.sh"is executed (/afs/desy.de/products/solaris/jumpstart/*) and this will copy more stuff to the client and anchor the "install_wgs_environment.sh" in /etc/init.d with a link from /etc/rc3.d on the client. Then a reboot is issued and the client boots and once it comes to "/etc/rc3.d/S20install_wgs_environment.sh" it will start the postinstall script.


5. The postinstall script.

Read it, you find it in
"
/afs/desy.de/products/solaris/jumpstart/install_wgs_environment.sh "
It is a collection of routines to

I tried to make it nice, readible and modular with comments, however it's long and calls other scripts (from other people) which might be not as easy to understand. ;) The procedure's the same for all supported Solaris releases and as of Aug. 99 it was redesigned.

6. Subdivided Subnets

Because we are short on class C subnets (for FDDI) we tend to divide these class C subnets into further subnets.   
Hints: Install the client at first ignoring the FDDI interface (omit simply the IP numbers). Afterwards install the FDDI packages (SUNWnft and SUNWnfr) run the
install_patches program again to make sure that the kernel drivers for FDDI are patched. After changing /etc/defaultrouter edit /etc/init.d/inetsvc and add after
/usr/sbin/ifconfig -au netmask + broadcast +
a line like:
/usr/sbin/ifconfig nf0 inet {my ip number} netmask {my subnetmask} broadcast {my broadcastadress}
You have also to make sure that the addition of the multicast route ( /usr/sbin/route add "224.0.0.0" "`uname -n`" 0 doesn't start in the foreground (simply add an ampersand at the end of the line).

7. Miscellaneous


Updated Jan 10 2002 Raymond Koluvek / DESY IT


Imprint © 2013 Last update: 22. Apr. 2002 www-it@desy.de