Process Overview

 1. Create profile server
 2. Create rules file
 3. Create profile
 4. test profile
 5. validate rules to create rules.ok file

Procedures

 1. create jumpstart directory on jumpstart server
 2. edit /etc/dfs/dfstab adding
    >share -F nfs -o ro,anon=0 /jumpstart_dir
 3. enter: shareall
 4. cd /cdrom_path/Solaris_2.6/Misc
 5. cp -r jumpstart_sample/* /jumpstart_dir
 6. edit /etc/bootparams adding line
    >* install_config=jumpstart_server:/jumpstart_dir
 7. create a rules file to point to the profile
 8. create a profile giving instructions on how to build (both of these can
    be modelled from example files)
 9. /usr/sbin/install.d/pfinstall -D -c /cdrom_path/s0 profile_name to check
    profile
10. run /jumpstart_dir/check to validate rules
    either
11. cd /cdrom_path/Solaris_2.6/Tools
    or
    copy cd on to disk using /cdrom_path/.../setup_install_server /directory
    the cd to the install directory
12. ./add_install_client -e ethernet_address_of_install_server -c servername:
    /jumpstart_dir hostname model
    e.g. ./add_install_client -e 08:00:20:89:71:34 -c suns01:/jumpstart
    suns02 sun4u
    Note:The target host must be defined on /etc/hosts
13. boot the install server from the OK prompt using: boot net - install

The jumpstart internal process

Phase 1

 1. boot net - install is entered at the OBP
 2. The client sends a RARP request to get it's IP address JS server replies
    with it.
 3. The client sends a TFTP request for the miniroot matching the IP address
 4. The jumpstart server supplies the miniroot
 5. client boots and
 6. loads the miniroot

Phase 2

 1. The client requests boot parameters from JS server
 2. Boot parameters are supplied from /etc/bootparams
 3. From this information, the client NFS mounts the specified directory on
    the root filesystem
 4. The client needs to know how to build itdelf so it mounts the sysidcfg
    file (if it's not on the same server) and uses the information in the
    file

Phase 3

 1. Client is now ready for software installation
 2. The client tries to access install-config as defined in /etc/bootparams
 3. If it's on a different server it is NFS mounted
 4. The client reads the rules.OK file from the directory
 5. A rule specifies which profile to use which in turn specifies the disk
    layout, which software cluster to use ,etc
 6. The rules.OK is checked again for any begin script to run and executes
    any found
 7. The contents of the profile are run including setting the locale and
    configuring disk partitions
 8. The software is now installed
 9. Once finished, customisation of configuration files and boot disk takes
    place.
10. Any finish script specified in the rules.OK is run.
11. The client reboots

/etc/bootparams specifies:

  • root = - the location of the miniroot image (on the boot server)
  • install= - the location of the install media (on the install server)
  • sysid_config= - the location of the sysidcfg file (on the configuration server)
  • install_config= - the location of the rules file (on the install server)

Recent Changes