USING JUMPSTART TO INSTALL/UPGRADE SYSTEMS OVER THE NETWORK

1. Load the software
   • Use the latest version AND hardware release of SunOS. By using the latest version, you get more fixes and features (yes, you get a little new breakage, but that's usually minor and the tradeoff is worth it) and you get more willing support from Sun. By using the latest _hardware_ release of the latest version, you get support for new hardware that was released after the original hardware release of the version you are using and you get a bunch of bundled patches, which allow you to slightly lower the priority of specifically adding the latest patches.
   • Pick a system to be your jumpstart server. You will want to keep the OS and the patches on it. Make sure you have at _least_ 500 MB available. You will need it. a 1 GB would be better. You really only need one system for this; for example, you don't have to put the acutal OS on a system on each subnet that you want to jump-start systems on (unless performance is going to be a real issue).

             # cd /cdrom/cdrom0
             # find s0 -depth -print | cpio -pdm /jumpstart_dir
             

2. Export the directory or file with the OS distribution.
   • The actual OS only has to be on ONE system (not one copy on each subnet, unless you think there is a speed issue). The system the OS is on does NOT have to be a Sun system.
   • Share the directory that the OS is on.

             # vi /etc/dfs/dfstab (for a SunOS 5 system)
             

     Add this line:

             share -o ro,anon=0 /top_dir_of_os_distrib
             

     You have to have both the "ro" and "anon=0" options. Relax. There are no company secrets int the distribution of the OS. Now run a unshareall and a shareall:

             # unshareall
             # shareall
             

3. Make sure the necessary network services are available

   You must have these available on at least one system on each subnet you plan to jump-start systems on.

   tftpd

   This has to be running for the OS to get its boot image. Check /etc/inetd.conf to make sure it is available (i.e. the tftpd entry should not be commented out). "kill -HUP" the inetd process if you had to uncomment tftpd.

           # vi /etc/inetd.conf
           (uncomment tftd)
           # kill -HUP inetd
           

   nfs services, rpc.bootparamd, in.rarpd

   After you have done the exports (shares), make sure nfs is running.

           # /etc/init.d/nfs.server stop
           # /etc/init.d/nfs.server start
           

4. Set up inetboot mini-os's

   You must do this on at least one system on each subnet you plan to jump-start systems on.

           # cd /js
           # cd $OS/usr/platform
           # for ARCH in sun4* ; do
           > cp -p $ARCH/lib/fs/nfs/inetboot /tftboot/inetboot.$ARCH.$OS
           > done
   

   The exact value of "$OS" may vary from release to release of the OS.

5. Add jump start server info to bootparams map (/etc/bootparams or NIS(+) maps)

   You must do this on at least one system on each subnet you plan to jump-start systems on. For example:

           fred.shmoe.com \
                   root=joe.shmoe.com:/js/SunOS-5.6/Solaris_2.6/Tools/Boot \
                   install=joe.shmoe.com:/js/SunOS-5.6 \
                   install_config=joe.shmoe.com:/js/install-config
   
           # Wildcards can be used to handle all other cases:
   
           * \
                   root=joe.shmoe.com:/js/SunOS-5.6/Solaris_2.6/Tools/Boot \
                   install=joe.shmoe.com:/js/SunOS-5.6 \
                   install_config=joe.shmoe.com:/js/install-config
           

6. Add hosts to ethers map (/etc/ethers or NIS(+) maps)

   Add the ethernet address of all hosts in question to the ethernet map. For example:

           8:0:20:6d:60:8d joe.shmoe.com
           

   You can find the ethernet address of a system while the OS by running dmesg | grep Ethernet You can find the ethernet address of a down system by typing reset at the 'ok' prompt.

7. Coordinate switching service

   Make sure that the "bootparams" and "ethers" entries in /etc/nsswitch.conf list the proper nameservice (either files, nis or nisplus) that you are using.

8. Configure install directory (optional)

   This is an optional way to eliminate questions during installation. Refer to Sun's documentation for more information on how to set this up.

   • Profile Configurations
     • 2.5.1 with 2 disks (Ultra 1)
     • 2.5.1 with 1 disk (Ultra 5,10)
     • 2.5.1 Upgrade from 2.5
     • 2.6 with 2 disks (Ultra 1)
     • 2.6 with 1 disk (Ultra 5,10)
     • 2.6 Upgrade from 2.5.1
   • Finish Scripts
     • 2.5.1 Initial Workstation
     • 2.5.1 Initial Server
     • 2.5.1 Upgrade from 2.5
     • 2.6 Initial Server
     • 2.6 Initial Workstation
   • Sample rules file
   • "pkgadd" admin file

9. Boot system

   On each system you wish to jump start:

           ok boot net - install
           

   Answer the questions. You should find that the install will take anywhere from 25 minutes to about one hour.

10. Hints

    The /tftboot entries can be rdisted as well as the /etc/bootparams and /etc/ethers files (it is not necessary to rdist the /etc/bootparams and /etc/ethers files if you are using NIS or NIS+).

11. Add entries for use
    • Assign IP address via DNS and NIS+
    • Determine HEX encoding of IP address via 'ip2hex' command.

              % ip2hex 192.168.2.51
                      C0A80233
                      

    • Create links in /tftpboot on tftp server

      To set up a machine to install Solaris 2.5.1 on a sun4u architexture:

              % ln -s /tftpboot/inetboot.sun4u.Solaris_2.5.1 /tftpboot/C0A80233
                      

    • Add ethernet address to ethers file. This must be done in the NIS+ tables as well as in the local /etc/ethers file on the tftp server!
    • Add appropriate entry to bootparams. This is done in the NIS+ table only.

      For a specific SunOS 5.5.1 machine:

              arrakis.varma.com root=petri:/pkg/adm/src/SunOS-5.5.1/export/exec/kvm/sparc.Solaris_2.5.1 \
              install=petri:/pkg/adm/src/SunOS-5.5.1 \
              boottype=:in \
              install_config=petri:/pkg/adm/slib/install
                      

      Default entry for SunOS 5.6 machines:

              * root=petri:/pkg/adm/src/SunOS-5.6/Solaris_2.6/Tools/Boot \
              install=petri:/pkg/adm/src/SunOS-5.6 \
              boottype=:in \
              install_config=petri:/pkg/adm/slib/install
                      

    • Create appropriate entry in the "rules" file, then run check
    • On the client, at the 'ok' prom prompt, type boot net - install
    • Answer initial questions