Difference between revisions of "JetWalkthrough"

From JetResources
Jump to: navigation, search
(No difference)

Revision as of 13:57, 29 August 2006

JET install and Configuration to server DHCP / PXE intel clients

Contributor: Paul Juster

Overview of my set up

I am using two Intel machines, my JumpStart server is sun1 ( and my JumpStart client vmclient needs to end up with a static IP (a flat network). Operating system is Solaris 10 x86.

On the JumpStart server I have already copied the Intel x86 DVD files to my server

# /cdrom/cdrom0/Solaris_10/Tools/setup_install_server /export/installx86

the alternative is to use the jet script to do this (/opt/SUNWjet/bin/copy_solaris_media).

In this example I am using JET 4.3 and I have only displayed lines in files that I changed from the default or that I want to make clear what the setting is.

Do not assume any of the below applied to a SPARC JET client

Download and Install the packages SUNWjet & documentation packages

Get JET from the Sun download centre (http://www.sun.com/downloads)

# bunzip2 jet.pkg.bz2
# pkgadd -d jet.pkg
 select Packages 10 & 11

JET Folder structure

I created/used the following folders

/export/pkgs  (not used but needed)
/export/patches (not used but needed)
/export/installx86 (Where the media has been copied too)

Note this is a simple configuration be in a larger setup /export/media should be used with sub folders for each media type.

JET NFS shares

The following shares were created to support JET.

("JET framework" share was automatically created during the package install)

# share
-               /opt/SUNWjet   ro,anon=0   "JET Framework"
-               /export/pkgs   ro,anon=0   "Jumpstart Media"
-               /export/installx86   ro,anon=0   "Jumpstart Media"
-               /export/patches   ro,anon=0   "Jumpstart Media"

Modify JET configuration

I edited /opt/SUNWjet/etc/jumpstart.conf to reflect my JET folder structure.

# This config file defines the jumpstart specific variables.

Adding Solaris Location

A “Solaris location” is a pointer to a folder containing the solaris installation media that has been copied to the JumpStart/JET server. The Solaris media is copied to the JET server in two ways

a. /cdrom/cdrom0/Solaris_10/Tools/setup_install_server b. /opt/SUNWjet/bin/copy_solaris_media

a. is the traditional JumpStart method (I used), b. is the JET method.

Once copied a “Solaris location” is needed for JET to reference and use, this is done by running

  1. /opt/SUNWjet/bin/add_solaris_location 10i /export/installx86

6. A “template”

A JET template outlines a JET clients configuration/installation and contains the answers to the installation questions that are normally asked (this is a very simplistic view as a lot more can be accomplish with the template). I created a template called vmclient

  1. /opt/SUNWjet/bin/make_template vmclient

7. Customise the template (DHCP/PXE) Once the template has been created some basic details needed to be added.

(I made the following changes and ignored all other lines at the moment) base_config_ClientArch=i86pc base_config_ClientEther=00:0c:29:76:fd:15 base_config_ClientOS=10i base_config_sysidcfg_nameservice=NONE base_config_sysidcfg_network_interface=PRIMARY base_config_sysidcfg_ip_address= base_config_sysidcfg_netmask= base_config_sysidcfg_root_password="boajrOmU7GFmY" base_config_sysidcfg_system_locale=en_GB.ISO8859-1 base_config_sysidcfg_timeserver=localhost base_config_sysidcfg_timezone="GB" base_config_sysidcfg_terminal=vt100 base_config_sysidcfg_security_policy=NONE base_config_sysidcfg_protocol_ipv6=no base_config_sysidcfg_default_route= base_config_client_allocation="grub"

Its worth noting that intel machine can only be built using JET/Jumpstart by using DHCP and PXE boot methods, in order for this to be configured within JET following line partly configures this.


8. DHCP server setup In order for JET to support an intel DHCP the DHCP server needs some basic details need to be added to /opt/SUNWjet/Products/base_config/solaris/make_dhcp file

  1. cat make_dhcp
  2. Synopsis: PXE boot pre-JUMP setups
  3. if DHCP server is not present, then activate it
  4. Change the NETWORK details to suit your own


dhcpconfig -D -r SUNWfiles -p /var/tmp

dhcpconfig -N ${NETWORK} -m ${NETMASK} -t ${ROUTER}

in order for these changes to be applied to the solaris dhcp server, permissions on the mae_dhcp file need to be changed so the file can be executed.

  1. ./make_dhcp

Created DHCP configuration file. Created dhcptab. Added "Locale" macro to dhcptab. Added server macro to dhcptab - sun1. DHCP server started. Added network macro to dhcptab - Created network table.

As you can see this has populated/configured the dhcp server with the basic settings, the client specific settings are added when make_client is run.

9. Populating JET with a client A client can now be added to the JET server using the make_client script.

  1. /opt/SUNWjet/bin/make_client -f vmclient

Gathering network information..

       Client: (
       Server: (, SunOS)

Solaris: client_prevalidate

        Clean up /etc/ethers

Solaris: client_build Creating sysidcfg Creating profile Adding base_config specifics to client configuration Solaris: Configuring JumpStart boot for vmclient

        Starting SMF services for JumpStart

Solaris: Configure PXE/grub build

        Adding install client
       Doing a TEXT based install
        Leaving the graphical device as the primary console
        Configuring vmclient macro
        Using local dhcp server
        PXE/grub configuration complete

Running '/opt/SUNWjet/bin/check_client vmclient'

       Client: (
       Server: (, SunOS)

Checking product base_config/solaris Checking Solaris boot image for critical patches (this may take a while..)

WARNING: Patch 119375-03 has not been applied to the boot image.

               This patch has been critical to the successful
               installation of the O/S.
               Please apply the patch with the command:
       # patchadd -C /export/installx86/Solaris_10/Tools/Boot 119375-03

Check of client vmclient -> Passed....

The obvious thing from this output is that it passed, but also you can see that a PXE/Grub build took place (which means that this client is an intel client) 10. Client boot.

The intelx86 client needs booting off the network, F12 is the normal key at boot time.

The intelx86 client gets an ip address

The grub loader is loaded

The grub loader load the multi boot image from the /tftpboot directory

and hopefully now installation windows/questions will be asked.

Reference files

11. Jumpstart.Conf @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

  1. This config file defines the jumpstart specific variables.
  2. Version: $Revision: 1.5 $
  3. Last Updated; $Date: 2006/02/04 12:08:58 $
  4. Location of the additional media for patches and packages:
  5. These paths should be URI form e.g. nfs://<serverip>/<path> or <path>
  6. Currently only PKG_DIR and PATCH_DIR can be on a remote NFS server.
  7. If they are just <path>, the appropriate address of the JumpStart server
  8. will be added.
  9. N.B. if the media location is on a different server, please ensure it is
  10. routable from the client !

JS_Default_Root_PW=boajrOmU7GFmY JS_BUILD_DIR=/var/opt/sun/jet JS_PKG_DIR=/export/pkgs JS_PATCH_DIR=/export/patches JS_SOLARIS_DIR=/export JS_DHCP_VENDOR="SUNW.Ultra-5_10 SUNW.Ultra-30"

  1. JS_CLIENT_MANAGEMENT="dhcp bootp"


12. make_dhcp @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ make_dhcp # This config file defines the dhcp variables.

  1. !/usr/bin/ksh
  2. Copyright 2005 Sun Microsystems, Inc. All rights reserved.
  3. Use is subject to license terms.
  4. Synopsis: PXE boot pre-JUMP setups
  5. if DHCP server is notpresent, then activate it
  6. Change the NETWORk details to suit your own


dhcpconfig -D -r SUNWfiles -p /var/tmp

dhcpconfig -N ${NETWORK} -m ${NETMASK} -t ${ROUTER}

13. template/vmclient @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

  1. Client template file
  2. Client: vmclient
  3. Created: Friday May 19 19:26:39 BST 2006
  4. This file was automatically generated using 'make_template'

  1. Product: base_config
  2. Synopsys: Basic host information
  1. Architecture type:
  2. sun4c : e.g. SS1, SS2, SS IPX
  3. sun4d : e.g. SS1000, SS2000
  4. sun4e : ?
  5. sun4m : e.g. SS LX, SS4, SS5, SS10, SS20
  6. sun4u : UltraSparc - U1, U2, E3x00, E4x00 etc
  7. sun4u1 : E10K
  8. sun4v : T2000
  9. i86pc : Intel X86
  10. Ethernet can be obtained from the 'banner' command at OBP
  11. OS is one of the values you used to register the solaris media using
  12. the add_solaris_location command

base_config_ClientArch=i86pc base_config_ClientEther=00:0c:29:76:fd:15 base_config_ClientOS=10i

  1. Client allocation
  2. The mechanism used to build this client; by default, the options listed
  3. in /opt/jet/etc/jumpstart.conf will be tried; you should only set this
  4. if this particular client needs to do something different.
  5. JET supports bootp, dhcp, and grub as allocation options.
  6. Currently grub is only supported on i86pc architectures.


  1. If you are using grub, you can set this variable to apply additional
  2. grub directives to the menu.lst.<MACADDRESS> file.


  1. products is the set of products to install after base_config; this
  2. should be updated automatically by make_template, so you
  3. will only need to change it, if you wish to omit certain
  4. modules when testing/debugging.


  1. JumpStart sysidcfg information
  2. The sysidcfg file provides information at initial boot time so that the
  3. system can properly identify itself. The interface and ip address defined
  4. here MUST be on the same subnet as the JumpStart server. The root password
  5. is set here also and must be written in encrypted format. The default value
  6. shown here is "newroot". The timeserver is normally the IP address of the
  7. JumpStart server.
  8. nameservice examples:
  9. NONE
  10. NIS { domain_name=uk.sun.com name_server=nis.uk.sun.com( }
  11. or for DNS
  12. DNS { domain_name=uk.sun.com name_server= search=uk.sun.com }
  13. network_interface:
  14. le0, hme0
  15. or PRIMARY (the default interface - net in OBP)
  16. N.B. PRIMARY is only valid from Solaris 7 upwards
  17. locale:
  18. en_UK for Solaris 2.6
  19. en_GB for Solaris 7 and above
  20. timeserver: Where the client gets the current time from.
  21. Leave blank to default the the JumpStart server
  22. Alternatively, set to 'localhost' to trust the current
  23. hardware clock on the client
  24. terminal: terminal type (vt100/vt220/sun etc)
  25. security_policy: Kerberos policy (Solaris 8 +)
  26. protocol_ipv6: Use ipv6 or not (Solaris 8 +)
  27. default_route: Solaris 9 allows a default route to be set
  28. (ignored on all other versions of Solaris, less than 9)

base_config_sysidcfg_nameservice=NONE base_config_sysidcfg_network_interface=PRIMARY base_config_sysidcfg_ip_address= base_config_sysidcfg_netmask= base_config_sysidcfg_root_password="boajrOmU7GFmY" base_config_sysidcfg_system_locale=en_GB.ISO8859-1 base_config_sysidcfg_timeserver=localhost base_config_sysidcfg_timezone="GB" base_config_sysidcfg_terminal=vt100 base_config_sysidcfg_security_policy=NONE base_config_sysidcfg_protocol_ipv6=no base_config_sysidcfg_default_route=

  1. X86, X64 specific settings. If this is an x86 client, then you may need
  2. to configure these settings. They are ignored for SPARC builds.
  3. base_config_x86_nowin:
  4. This stops Solaris from trying to run windows during the install.
  5. the default value is yes.
  6. base_config_x86_console:
  7. Set the console to the correct tty port. This is used for doing installs
  8. via the serial port or the SP. b1600,v20z and v40z use ttya. lx50, v60x,
  9. and v65x use ttyb. NOTE: you only need to set this if you are NOT going
  10. to connect a keyboard and monitor to the client.
  11. base_config_x86_disable_acpi:
  12. Disable ACPI - sometimes disabling ACPI makes the install go
  13. better due to how the interrupts are handled. Non-Null disables ACPI.
  14. base_config_x86_safetoreboot:
  15. The Solaris installer can't control the BIOS, therefore does not
  16. know if its safe to reboot the client as it may simply jumpstart
  17. again. If your PXE boot is a one time option, and the next reboot
  18. will attempt to boot from disk, then you probably want to set this
  19. option to "yes". Otherwise, leave it as it is so that it won't reboot
  20. and therefore allow you to manually change your BIOS to boot from disk.
  21. base_config_x86_disable_kdmconfig:
  22. X86 systems sometimes go interactive on the first reboot (Bug 6321043)
  23. on Solaris 10 Update 1. Setting this parameter will stop this from
  24. happenning.
  25. base_config_x86_confflags
  26. The parameters specified for this variable are passed directly to
  27. add_install_client -b confflags= option.
  28. For e.g., by specifying,
  29. base_config_x86_confflags="-f -P/boot/solaris/dca"
  30. add_install_client is called with -b confflag="-f -P /boot/solaris/dca"
  31. option.
  32. base_config_sysidcfg_x86_kdmfile
  33. Append the file specified here to sysidcfg file.
  34. This variable can reference a file relative to the
  35. Clients/<clientname> directory or a absolute path.

base_config_x86_nowin="yes" base_config_x86_console="" base_config_x86_disable_acpi="" base_config_x86_safetoreboot="" base_config_x86_disable_kdmconfig="" base_config_x86_confflags="" base_config_sysidcfg_x86_kdmfile=""

  1. Want to create your own custom profile ? if so, use this variable to
  2. reference a file relative to the Clients/<clientname> directory or
  3. absolute path, otherwise fill in the other details below to get toolkit
  4. to create one for you.
  5. If absolute path is specified, then the profile file is copied
  6. to Clients/<clientname> directory.


  1. OR fill out the base_config_profile variables below.
  2. JumpStart profile information
  3. A limited profile can be automatically generated here. If further
  4. customisation is required, then you can manually create a profile in the
  5. client directory and reference it in the base_config_profile variable.
  6. Cluster:
  7. SUNWCrnet : Minimal. Solaris 10 only
  8. SUNWCreq : Required - really basic, good for testing
  9. SUNWCuser : User collection
  10. SUNWCprog : User + Developers collection
  11. SUNWCall : All packages
  12. SUNWCXall : All + OEM packages (mandatory for E10K)
  13. usedisk: defines the disk that the OS will be loaded on to - bootdisk
  14. (if this is set to rootdisk. , then the current boot disk will
  15. be used)
  16. dontuse: defines disks that should not be used..
  17. ** N.B. This will only be used if 'usedisk' is NOT set
  18. Space seperated list of disks of the form c?t?d?
  19. partition sizes:
  20. if partitions are not required simply leave blank. In order to maintain
  21. consistency the partitions will always use the same slice number:
  22. / s0
  23. swap s1
  24. We've prepopulated the remaining slices based on Sun defaults,
  25. but you can change this.
  26. /var s5
  27. /usr s6
  28. /opt s7
  29. at most one partition can have the size 'free' which denotes all the
  30. unallocated/spare space on a disk.

base_config_profile_cluster=SUNWCXall base_config_profile_usedisk=rootdisk.


base_config_profile_root=free base_config_profile_swap=256

  1. If you are using VxVM and want your boot disk to look like the mirror, then
  2. leave slices 3 and 4 empty. If you do not care about keeping the two disks
  3. looking cosmetically the same, please just make sure you have two free slices
  4. somewhere on the disk for VxVM!
  5. If you are not using VxVM, then you can use s3 and s4 for whatever you wish!

base_config_profile_s3_mtpt="" base_config_profile_s3_size=""

base_config_profile_s4_mtpt="" base_config_profile_s4_size=""

base_config_profile_s5_mtpt="/var" base_config_profile_s5_size=""

base_config_profile_s6_mtpt="/usr" base_config_profile_s6_size=""

  1. If you are using DiskSuite, the default behaviour is to use slice 7 as a
  2. location for metastate databases. If you are using DiskSuites default config,
  3. please avoid using s7 for data!

base_config_profile_s7_mtpt="/opt" base_config_profile_s7_size=""

  1. You can specify additional disks to use/configure here
  2. additional_disks is a space separated list of c?t?d? type disk names
  3. For each disk listed in additional_disks, a pair of variables of the form
  4. base_config_profile_disk_c?t?d?s?_mtpt="...."
  5. base_config_profile_disk_c?t?d?s?_size="...."
  6. should be defined for each slice required on the disk.


  1. Additional locales/geos e.g. N_Europe, C_Europe

base_config_profile_add_locales="" base_config_profile_del_locales=""

base_config_profile_add_geos="" base_config_profile_del_geos=""

  1. UFS Logging
  2. Solaris 7 and above support UFS+, which allows for a logging filesystem
  3. under UFS. If you want to use this feature on any of the UFS mount points,
  4. please specify the mount points here, as a space seperated list, or enter
  5. the keyword "all" to enable logging on all UFS filesystems.
  6. Solaris 9 09/04 enables logging by default. You can also specify mountpoints
  7. preceded by a - sign to say that you DON'T want logging enabled on that
  8. filesystem, or you can use the keyword "none" to say you don't want any
  9. ufs logging turned on at all.
  10. N.B. root (/) can be included in the list, and is included by default if
  11. using either the "all" or "none" keyword.
  12. Finally, you can't mix keywords and mountpoints. i.e. "all -/" is NOT
  13. valid.
  14. e.g. base_config_ufs_logging_filesys="all" : log all filesystems
  15. base_config_ufs_logging_filesys="none" : log no filesystems
  16. base_config_ufs_logging_filesys="-/ /var -/usr"  : log /var, but not / and /usr.


  1. Packages to add to/remove from the selected cluster
  2. Use this to populate the profile with package <pkg> <add|delete> entries

base_config_profile_add_packages="" base_config_profile_del_packages=""

  1. Clusters to add to/remove
  2. Use this to populate the profile with cluster <cluster> <add|delete> entries

base_config_profile_add_clusters="" base_config_profile_del_clusters="SUNWCpm SUNWCpmx SUNWCdial SUNWCdialx"

  1. Remote file systems (NFS)
  2. Specify these as space seperated list of pairs as follows, using ? as
  3. the seperator (as : has special meanings with nfs!)
  4. e.g. to mount on /fs you would create the entry
  5. base_config_nfs_mounts="fs?"


  1. Host information
  2. This section defines most things network related etc.
  3. In addtion, if the machine will be JumpStarted as one name/address and
  4. needs to have a different name/address once installed, this is where you
  5. can set that information.
  6. nodename: the value for /etc/nodename if it's not the default
  7. hostname
  8. defaultrouter: the value for /etc/defaultrouter.
  9. notrouter: if this is set, the file /etc/notrouter will be created
  10. dns_domain: domain entry for /etc/resolv.conf
  11. dns_nameservers: nameserver entries for /etc/resolv.conf
  12. (list of ip addresses, space separated)
  13. dns_searchpath: list of entries to go in the search line
  14. dns_disableforbuild: If there is no DNS available in the build
  15. environment, set this to delay the configuration
  16. of DNS until later on.

base_config_nodename="" base_config_defaultrouter="" base_config_notrouter=""

base_config_dns_domain="" base_config_dns_nameservers="" base_config_dns_searchpath=""


  1. NTP configuration
  2. Specify a list of names or ip addresses for the NTP servers. The first
  3. one will be given a 'prefer' tag. This section will only place lines
  4. of the form: server <ipaddress/name> [prefer]
  5. into the /etc/inet/ntp.conf file. If you require more control of ntp,
  6. please use the custom module to deploy your own custom ntp.conf file.
  7. N.B. If you do use names, they must be resolvable in your name service.


  1. Network Interface information
  2. networkifs: a list of interfaces to be defined,
  3. space seperated "le0 hme0".
  4. N.B. the sysidcfg interface will already be configured
  5. Logical interfaces should be defined using _'s rather
  6. than :'s.
  7. networkif_<ifname>: the details of the interface <if>
  8. "netname netmask hostname address"
  9. netname: arbritrary name for /etc/networks
  10. netmask: netmask of this if (e.g.
  11. hostname: unique hostname (N.B. not multihomed)
  12. address: IP address of this interface
  13. For example:
  14. base_config_networkifs="ge0 ge0_1"
  15. base_config_networkif_ge0="bkp me-bkp"
  16. base_config_networkif_ge0_1="bkp2 me-bkp2"

base_config_networkifs="" base_config_networkif_le0=""

  1. N.B. Logical interfaces MUST use _ rather than : as illustrated below


  1. IP Multipathing (Solaris 8+)
  2. IPMP default mode is automatic failback.
  3. To change this mode edit /etc/default/mpathd
  4. ipmp_networkifs: a list of interfaces to be defined under ipmp control
  5. a space separated list of pairs only
  6. e.g. "qfe0_qfe4 qfe1_qfe5"
  7. N.B. If the primary interface is used in an ipmp group, the
  8. system must be rebooted manually after installation to
  9. activate ipmp.
  10. N.B. Can only setup ipmp group with pairs of interfaces in one
  11. of the following configurations:
  12. active-standby failover:
  13. Set ipmp mode = s, and specify one logical
  14. hostname/ip address pair.
  15. failover with outbound load spreading:
  16. Set ipmp mode = l, and specify one logical
  17. hostname/ip address pair.
  18. active-active with outbound load spreading:
  19. Set ipmp mode = l, specify a second logical
  20. hostname/ip address pair for the second interface.
  21. ipmp_networkif_<if>_<if>: "netgroup mode test1 test2 mask hostname log-ip hostname2 log-ip2"
  22. details of the interfaces in the ipmp group
  23. e.g. networkif_ipmp_qfe0_qfe4
  24. netgroup: ipmp interface group name
  25. e.g. database-net
  26. ipmp mode: s = standby (failover only)
  27. ** test addresses are allocated last,
  28. ** first test address will be on the
  29. ** first virtual interface of the
  30. ** first physical adapter. Second
  31. ** test address will be on the second
  32. ** physical adapter.
  33. l = load spreading / active-active
  34. ** test addresses are allocated on
  35. ** first virtual interfaces on both
  36. ** the first and second physical
  37. ** adapters.
  38. To force the test addresses onto the physical
  39. adapters, use the suffix 'p' to the above
  40. modes, i.e. 'sp' or 'lp'. This is not
  41. recommended and may break certain applications.
  42. test1: ipmp test address1
  43. test2: ipmp test address2
  44. N.B. these addresses must not be used or
  45. placed in the hosts file
  46. mask: netmask for ipmp pair
  47. hostname: unique hostname for logical ip
  48. log-ip: logical ip address for first i/f of pair
  49. N.B. The following two parameters are for active-active
  50. configurations only. Do not specify them for an
  51. active-standby configuration.
  52. hostname2: unique hostname for logical ip
  53. log-ip2: logical ip address for second i/f
  54. of pair
  55. IPMP on Solaris 10.
  56. If you are running Solaris 10, you can optionally configure the
  57. system to have NO test addresses. In this case, the ipmp mode should be set
  58. to "ln" or "sn" depending on whether you want outbound load spreading or
  59. not and the 2 test addresses do not need to be privided.
  60. Examples:
  61. --------
  62. base_config_ipmp_networkifs="qfe0_qfe1"
  63. Outbound load spreading 2 hostnames, test on virtual interfaces.
  64. base_config_ipmp_networkif_qfe0_qfe1="db l 24 oracle-db apache"
  65. Outbound load spreading 1 hostname, test on physical interfaces.
  66. base_config_ipmp_networkif_qfe0_qfe1="db lp 24 oracle-db"
  67. Failover, 1 hostname, test on physical interfaces.
  68. base_config_ipmp_networkif_qfe0_qfe1="db sp 24 oracle-db"
  69. Failover, 1 hostname, no test addresses (Sol 10 only).
  70. base_config_ipmp_networkif_qfe0_qfe1="db sn 24 oracle-db"

base_config_ipmp_networkifs="" base_config_ipmp_networkif_qfe0_qfe1=""

  1. Misc options
  2. this section is a catchall for other options not included above
  3. update_terminal: if set, put the sysidcfg terminal type into inittab
  4. enable_savecore: if set to any value, enable save core (Solaris 2.6 only)
  5. dumpadm_minfree: set a limit so that crash dumps don't fill up the
  6. dump filesystem. See dumpadm(1M) -m option for
  7. possible values.
  8. noautoshutdown: if set to any value, disable power management
  9. enable_rootlogin: if set to any value, enable network root login
  10. from both telnet/rsh and ssh
  11. enable_rootftp: if set to any value, enable root ftp access
  12. shutup_sendmail: if set, create an alias hostname. to shut up sendmail
  13. poweroff_afterbuild: if set, shut the machine down once it has been built
  14. base_config_dedicated_dump_device:
  15. if set, dumpadm will configure the partition as a
  16. Dedicated Dump Device. See dumpadm(1M) for supported
  17. Operating Environments.
  18. (Device path e.g. /dev/dsk/c?t?d?s?)
  19. N.B. This partition is for the SOLE use of the crashdump utility !
  20. enable_altbreak: if set, enable alternate break sequence
  21. disable_sysid_probe: if set, skip the sysid stuff on the first reboot; this
  22. usually just tries to rarp ip addresses for additional
  23. interfaces and takes *ages* on machines with lots
  24. of unused network adapters.

base_config_update_terminal="yes" base_config_enable_savecore="yes" base_config_dumpadm_minfree="20000k" base_config_noautoshutdown="pm_disabled" base_config_enable_rootlogin="" base_config_enable_rootftp="" base_config_shutup_sendmail="" base_config_poweroff_afterbuild="" base_config_dedicated_dump_device="" base_config_enable_altbreak="" base_config_disable_sysid_probe=""

  1. NFSv4
  2. Set up the NFSv4 domain to prevent being prompted at first reboot.
  3. If not set, this will default to the entry in base_config_dns_domain,
  4. and if that is not set, to the value 'domain', which is the default
  5. in /etc/default/nfs


  1. N.B. Unless you need to point this client at alternate media for patches
  2. and packages that is not held on this server, please skip this section!
  3. productdir is where to find the products. This should be a URI style
  4. path, i.e. nfs:// If the server
  5. is the JumpStart server, then it should just be specified
  6. as a normal path.
  7. patchdir is where to find the patches. Same format as productdir.
  8. --------------------------------------------------------------------------
  9. Leaving the following blank means they will be populated using jumpstart.conf
  10. and the JumpStart servers ip address. This is the default behaviour
  11. and should only be changed if your patch/package repository is not held
  12. on this server.
  13. --------------------------------------------------------------------------

base_config_productdir="" base_config_patchdir=""

  1. Last one - mainly for developing JumpStart scripts!
  2. If you set this, the rc3.d/S99jumpstart script will be disabled
  3. (set to rc3.d/s99jumpstart) every time it is processed - this allows you
  4. to run it by hand and invoke each reboot step
  5. This does not work on Solaris 10.


@@@Other JET configurations@@@

14. JET Sparc_DHCP > I now want to configure JET for a basic sparc DHCP and > bootp build. > > For Sparc DHCP do I just need to make the following > changes… > > Create a template with the > base_config_client_allocation equal "dhcp" > yep > edit /opt/SUNWjet/etc/Jumpstart.conf to add uname –i > to JS_DHCP_VENDOR="SUNW.Ultra-5_10 SUNW.Ultra-30" to > reflect my wanting to use SPARC & DHCP. > yep > And I assume make_client will create the appropriate > settings in dhcpmgr etc. > uh huh > Anything else ? > 15. JET Sparc_Bootp

> For Sparc bootp do I just need to create a template > with the base_config_client_allocation equal "bootp" > yep

> And I assume make_client will create the appropriate > settings in tftpboot etc. > uh huh

> I will not be able to test this for a week or so, as > so far all my testing has been done using Vmware > locally on my laptop.

16. Changing the media location > > And finally I will in the future want to change my > media location from /export/install to > /export/jumpstart/s10i & /export/jumpstart/s10sparc > etc. > > I guess I will need to update my “solaris locations” > will I need to make JS_SOLARIS_DIR=/export/jumpstart > in jumpstart.conf ? anything else ? > Only thing that matters is the solaris media locations. The JS_SOLARIS_DIR only affects the location of the media when you use the JET copy_solaris_media command, otherwise it is immaterial. In other words, once your /opt/SUNWjet/etc/solaris_media_locations file is vaild, everthing should be hunky dory.