aa90faddd01 howto setup jumpstart

8/7/2019 AA90FADDd01 Howto setup jumpstart

1/5

Jumpstart : Howto setup a Jumpstart Server(Nov 02, 2004 at 02:02 PM) - Written by James Spurin - Last Updated (Nov 02, 2004 at 02:48 PM)

Jumpstart Server Howto :For this example I will be using skippy as the hostname for the jumpstart server and hotdog for the client.

Create a partition that will be used to store the jumpstart configuration, I have a spare disk free so I will be using

c0t1d0s2 for this example.root@skippy: newfs /dev/dsk/c0t1d0s2root@skippy: mkdir /jumpstartroot@skippy: mount /dev/dsk/c0t1d0s2 /jumpstart(add appropriate entry to /etc/vfstab) /dev/dsk/c0t1d0s2 /dev/rdsk/c0t1d0s2 /jumpstart ufs 1 yes - As our jumpstart server may support different Solaris versions I will setup the system using the hierarchy/jumpstart/OS/Version-Release

I will be using Solaris 9 Release 0404 for this exampleroot@skippy: mkdir -p /jumpstart/OS/Solaris_9-0404Insert the Solaris Software 1/2 CD.root@skippy: cd /cdrom/sol_9_404_sparc/s0/Solaris_9/ToolsThe following command copies enough software for Core, End-User or Developer installations

root@skippy: ./setup_install_server /jumpstart/OS/Solaris_9-0404/Verifying target directory...Calculating the required disk space for the Solaris_9 productCalculating space required for the installation boot imageCopying the CD image to disk...Copying Install Boot Image hierarchy...Install Server setup complete(This took approx 20 minutes to complete)

root@skippy: cd (move out of the cdrom directory so we can unmount)root@skippy: eject

Insert the Solaris Software 2/2 CD.root@skippy: cd /cdrom/cdrom0/Solaris_9/Tools/This adds support for the Entire Distribution and Entire Distribution plus OEM installations as well as some other bits nbobs.root@skippy: ./add_to_install_server /jumpstart/OS/Solaris_9-0404/

The following Products will be copied to /jumpstart/OS/Solaris_9-0404/Solaris_9/Product:Solaris_2_of_2If only a subset of products is needed enter Control-Chttp://www.twitchy.net/mambo - Twitchy.net Powered by Mambo Generated:31 May, 2010, 03:12


2/5

and invoke ./add_to_install_server with the -s option.Checking required disk space...Copying the Early Access products...325296 blocks

Copying Top Level installer...55328 blocksCopying Tools Directory...3568 blocksProcessing completed successfully.(Approx 11 minutes)

Next copy some of the jumpstart configuration files provided by Sun -.root@skippy: cd /jumpstart/OS/Solaris_9-0404/Solaris_9/Misc/jumpstart_sample/root@skippy: lsany_machine host_class rules upgrade x86-begin.confcheck net924_sun4c set_root_pw x86-begin x86-classroot@skippy: cp rules /jumpstart/root@skippy: cp check /jumpstart/To keep the jumpstart server tidy we will create a directory for preconfigartion scripts with the following hierarchy

/jumpstart/Sysidcfg/Solaris_x/sysidcfgroot@skippy: mkdir -p /jumpstart/Sysidcfg/Solaris_9root@skippy: cd /jumpstart/Sysidcfg/Solaris_9root@skippy: vi sysidcfgsystem_locale=en_GBtimezone=GBtimeserver=localhostname_service=NONEsecurity_policy=NONE

root_password=""network_interface=PRIMARY { protocol_ipv6=no

netmask=255.255.255.0default_route=NONE }

terminal=vt100root@skippy: cd /jumpstart/The rules file we copied is good for reference but we will create our own -root@skippy: mv rules rules.origroot@skippy: vi rulesany - - Profiles/any_machine Finish/finish_scriptTo keep the jumpstart server neat it is a good idea to keep system profiles seperate.

I use the catchall profile called any_machine, if you are setting up multiple configurations this file would be useful as ahttp://www.twitchy.net/mambo - Twitchy.net Powered by Mambo Generated:31 May, 2010, 03:12


3/5

template.root@skippy: mkdir /jumpstart/Profilesroot@skippy: cd /jumpstart/Profiles/root@skippy: vi any_machineinstall_type initial_installsystem_type standalonepartitioning explicit

cluster SUNWCXallfilesys rootdisk.s0 4096 /filesys rootdisk.s1 512 swapfilesys rootdisk.s3 1024 /varfilesys rootdisk.s4 20 unnamedfilesys rootdisk.s6 free unnamedWe will create a basic finish script. For further customization remember to specify the root slice as /a.root@skippy: mkdir /jumpstart/Finishroot@skippy: cd /jumpstart/Finish/root@skippy: vi finish_scripttouch /a/noautoshutdown

Make the finish script executable by allroot@skippy: chmod a+rx finish_scriptCheck the configuration is okay with the check scriptroot@skippy: cd /jumpstartroot@skippy: ./checkValidating rules...Validating profile Profiles/any_machine...The custom JumpStart configuration is ok.root@skippy: ls rules.ok

rules.okAdd the new clients information to the hosts and ethers filesroot@skippy: vi /etc/hosts172.17.4.123 hotdogroot@skippy: vi /etc/ethers8:0:20:d1:d4:5b hotdogThe following command is used to finish the setup for the new client -

-c (configuration e.g. path to rules) -s (Solaris installation image) -p (preconfiguration e.g. sysidcfg)hotdog sun4u = hostname and architececture typeroot@skippy: cd /jumpstart/OS/Solaris_9-0404/Solaris_9/Tools/root@skippy: ./add_install_client -c skippy:/jumpstart -s skippy:/jumpstart/OS/Solaris_9-0404 -p skippy:/jumpstart/Sysidcfg/Solaris_9 hotdog sun4usaving original /etc/dfs/dfstab in /etc/dfs/dfstab.origAdding "share -F nfs -o ro,anon=0 /jumpstart/OS/Solaris_9-0404" to /etc/dfs/dfstabmaking /tftpbootenabling tftp in /etc/inetd.confstarting rarpdstarting bootparamdstarting nfsd'sstarting nfs mountdhttp://www.twitchy.net/mambo - Twitchy.net Powered by Mambo Generated:31 May, 2010, 03:12


4/5

updating /etc/bootparamscopying inetboot to /tftpbootChecking /tftpboot we can see that the necessary inetboot files have been created with a hex conversion to our macaddress.root@skippy: ls /tftpbootAC11047B rm.172.17.4.123

AC11047B.SUN4U tftpbootinetboot.SUN4U.Solaris_9-1The bootparams file has been populated with the information we provided to add_install_clientroot@skippy: cat /etc/bootparamshotdog root=skippy:/jumpstart/OS/Solaris_9-0404/Solaris_9/Tools/Bootinstall=skippy:/jumpstart/OS/Solaris_9-0404boottype=:in sysid_config=skippy:/jumpstart/Sysidcfg/Solaris_9 install_config=skippy:/jumpstart rootopts=:rsize=32768To enable a successful non interactive jumpstart the path to the Solaris installation image and jumpstart configurationneeds to be shared via NFS. As we can see from above "add_install_client" command has added an entry to

/etc/dfs/dfstab for the Solaris installation image but nothing for the jumpstart configuration directory.

As our setup uses /jumpstart as the base directory changing the entry in /etc/dfs/dfstab to reflect this will allow both theInstallation image and the configuration directory to be mounted via NFS.root@skippy: cat /etc/dfs/dfstab# Place share(1M) commands here for automatic execution# on entering init state 3.## Issue the command '/etc/init.d/nfs.server start' to run the NFS

# daemon processes and the share commands, after adding the very# first entry to this file.## share [-F fstype] [ -o options] [-d ""] [resource]# .e.g,# share -F nfs -o rw=engineering -d "home dirs" /export/home2share -F nfs -o ro,anon=0 /jumpstart/OS/Solaris_9-0404root@skippy: vi /etc/dfs/dfstab"/etc/dfs/dfstab" 13 lines, 448 characters

# Place share(1M) commands here for automatic execution# on entering init state 3.## Issue the command '/etc/init.d/nfs.server start' to run the NFS# daemon processes and the share commands, after adding the very# first entry to this file.## share [-F fstype] [ -o options] [-d ""] [resource]# .e.g,# share -F nfs -o rw=engineering -d "home dirs" /export/home2share -F nfs -o ro,anon=0 /jumpstartroot@skippy: unshareallroot@skippy: shareallroot@skippy: dfsharesRESOURCE SERVER ACCESS TRANSPORT

skippy:/jumpstart skippy - -http://www.twitchy.net/mambo - Twitchy.net Powered by Mambo Generated:31 May, 2010, 03:12


5/5

The jumpstart server setup is complete. The client can now be installed by issuing the following from the OBP -{0} ok boot net - install

http://www.twitchy.net/mambo - Twitchy.net Powered by Mambo Generated:31 May, 2010, 03:12

aa90faddd01 howto setup jumpstart

Documents