JetWalkthrough - Revision history

Paul at 09:01, 30 August 2006

2006-08-30T09:01:16Z

Paul at 08:49, 30 August 2006

2006-08-30T08:49:51Z

Marty at 13:12, 29 August 2006

2006-08-29T13:12:05Z

Show changes

Marty at 13:04, 29 August 2006

2006-08-29T13:04:20Z

Show changes

Marty at 12:57, 29 August 2006

2006-08-29T12:57:19Z

New page

== 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'' (192.168.0.250) and my JumpStart client ''vmclient'' needs to end up with a static IP 192.168.0.200 (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.
#
JS_PKG_DIR=/export/pkgs
JS_PATCH_DIR=/export/patches
JS_SOLARIS_DIR=/export

=== 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

# /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

# /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=192.168.0.200
base_config_sysidcfg_netmask=255.255.255.0
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=192.168.0.254
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.

base_config_client_allocation="grub"

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
# cat make_dhcp
################################################################################
# Synopsis: PXE boot pre-JUMP setups
# if DHCP server is not present, then activate it
#
# Change the NETWORK details to suit your own
NETWORK=192.168.0.0
NETMASK=255.255.255.0
ROUTER=192.168.0.254

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.

# ./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 - 192.168.0.0.
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.

# /opt/SUNWjet/bin/make_client -f vmclient
Gathering network information..
Client: 192.168.0.200 (192.168.0.0/255.255.255.0)
Server: 192.168.0.250 (192.168.0.0/255.255.255.0, 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: 192.168.0.200 (192.168.0.0/255.255.255.0)
Server: 192.168.0.250 (192.168.0.0/255.255.255.0, 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
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
# This config file defines the jumpstart specific variables.
#
# Version: $Revision: 1.5 $
# Last Updated; $Date: 2006/02/04 12:08:58 $
#
# Location of the additional media for patches and packages:
#
# These paths should be URI form e.g. nfs://<serverip>/<path> or <path>
# Currently only PKG_DIR and PATCH_DIR can be on a remote NFS server.
# If they are just <path>, the appropriate address of the JumpStart server
# will be added.
#
# N.B. if the media location is on a different server, please ensure it is
# 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"
#JS_CLIENT_MANAGEMENT="dhcp bootp"
JS_CLIENT_MANAGEMENT="bootp"

12. make_dhcp
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
make_dhcp # This config file defines the dhcp variables.
#!/usr/bin/ksh
#
# Copyright 2005 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
################################################################################
#
# Synopsis: PXE boot pre-JUMP setups
# if DHCP server is notpresent, then activate it
#
# Change the NETWORk details to suit your own
NETWORK=192.168.0.0
NETMASK=255.255.255.0
ROUTER=192.168.0.254

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

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

13. template/vmclient
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
###############################################################################
#
# Client template file
#
# Client: vmclient
# Created: Friday May 19 19:26:39 BST 2006
#
# This file was automatically generated using 'make_template'
###############################################################################

###############################################################################
#
# Product: base_config
#
# Synopsys: Basic host information
#
###############################################################################

############
#
# Architecture type:
# sun4c : e.g. SS1, SS2, SS IPX
# sun4d : e.g. SS1000, SS2000
# sun4e : ?
# sun4m : e.g. SS LX, SS4, SS5, SS10, SS20
# sun4u : UltraSparc - U1, U2, E3x00, E4x00 etc
# sun4u1 : E10K
# sun4v : T2000
#
# i86pc : Intel X86
#
# Ethernet can be obtained from the 'banner' command at OBP
#
# OS is one of the values you used to register the solaris media using
# the add_solaris_location command
#
base_config_ClientArch=i86pc
base_config_ClientEther=00:0c:29:76:fd:15
base_config_ClientOS=10i

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

# If you are using grub, you can set this variable to apply additional
# grub directives to the menu.lst.<MACADDRESS> file.
#
base_config_grub_append=""

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

############
#
# JumpStart sysidcfg information
#
# The sysidcfg file provides information at initial boot time so that the
# system can properly identify itself. The interface and ip address defined
# here MUST be on the same subnet as the JumpStart server. The root password
# is set here also and must be written in encrypted format. The default value
# shown here is "newroot". The timeserver is normally the IP address of the
# JumpStart server.
#
# nameservice examples:
# NONE
# NIS { domain_name=uk.sun.com name_server=nis.uk.sun.com(129.159.91.1) }
# or for DNS
# DNS { domain_name=uk.sun.com name_server=192.168.1.1 search=uk.sun.com }
#
# network_interface:
# le0, hme0
# or PRIMARY (the default interface - net in OBP)
# N.B. PRIMARY is only valid from Solaris 7 upwards
#
# locale:
# en_UK for Solaris 2.6
# en_GB for Solaris 7 and above
#
# timeserver: Where the client gets the current time from.
# Leave blank to default the the JumpStart server
#
# Alternatively, set to 'localhost' to trust the current
# hardware clock on the client
#
# terminal: terminal type (vt100/vt220/sun etc)
#
# security_policy: Kerberos policy (Solaris 8 +)
#
# protocol_ipv6: Use ipv6 or not (Solaris 8 +)
#
# default_route: Solaris 9 allows a default route to be set
# (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=192.168.0.200
base_config_sysidcfg_netmask=255.255.255.0
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=192.168.0.254

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

#
#
#
#
#######

#
# Want to create your own custom profile ? if so, use this variable to
# reference a file relative to the Clients/<clientname> directory or
# absolute path, otherwise fill in the other details below to get toolkit
# to create one for you.
#
# If absolute path is specified, then the profile file is copied
# to Clients/<clientname> directory.
#
base_config_profile=""
#
#######
# OR fill out the base_config_profile variables below.
############
#
# JumpStart profile information
#
#
# A limited profile can be automatically generated here. If further
# customisation is required, then you can manually create a profile in the
# client directory and reference it in the base_config_profile variable.
#
# Cluster:
# SUNWCrnet : Minimal. Solaris 10 only
# SUNWCreq : Required - really basic, good for testing
# SUNWCuser : User collection
# SUNWCprog : User + Developers collection
# SUNWCall : All packages
# SUNWCXall : All + OEM packages (mandatory for E10K)
#
# usedisk: defines the disk that the OS will be loaded on to - bootdisk
# (if this is set to rootdisk. , then the current boot disk will
# be used)
#
# dontuse: defines disks that should not be used..
# ** N.B. This will only be used if 'usedisk' is NOT set
# Space seperated list of disks of the form c?t?d?
#
# partition sizes:
#
# if partitions are not required simply leave blank. In order to maintain
# consistency the partitions will always use the same slice number:
#
# / s0
# swap s1
#
# We've prepopulated the remaining slices based on Sun defaults,
# but you can change this.
# /var s5
# /usr s6
# /opt s7
#
# at most one partition can have the size 'free' which denotes all the
# unallocated/spare space on a disk.
#
base_config_profile_cluster=SUNWCXall
base_config_profile_usedisk=rootdisk.

base_config_profile_dontuse=""

base_config_profile_root=free
base_config_profile_swap=256

#
# If you are using VxVM and want your boot disk to look like the mirror, then
# leave slices 3 and 4 empty. If you do not care about keeping the two disks
# looking cosmetically the same, please just make sure you have two free slices
# somewhere on the disk for VxVM!
#
# 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=""

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

base_config_profile_s7_mtpt="/opt"
base_config_profile_s7_size=""
#
############

############
#
# You can specify additional disks to use/configure here
#
# additional_disks is a space separated list of c?t?d? type disk names
#
# For each disk listed in additional_disks, a pair of variables of the form
#
# base_config_profile_disk_c?t?d?s?_mtpt="...."
# base_config_profile_disk_c?t?d?s?_size="...."
#
# should be defined for each slice required on the disk.
#
# N.B. DO NOT SET THE BOOT DISK UP HERE !
#
base_config_profile_additional_disks=""

############
#
# 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=""

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

############
#
# Packages to add to/remove from the selected cluster
#
# Use this to populate the profile with package <pkg> <add|delete> entries
#
base_config_profile_add_packages=""
base_config_profile_del_packages=""

############
#
# Clusters to add to/remove
#
# 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"

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

############
#
# Host information
#
# This section defines most things network related etc.
#
# In addtion, if the machine will be JumpStarted as one name/address and
# needs to have a different name/address once installed, this is where you
# can set that information.
#
# nodename: the value for /etc/nodename if it's not the default
# hostname
#
# defaultrouter: the value for /etc/defaultrouter.
#
# notrouter: if this is set, the file /etc/notrouter will be created
#
# dns_domain: domain entry for /etc/resolv.conf
#
# dns_nameservers: nameserver entries for /etc/resolv.conf
# (list of ip addresses, space separated)
#
# dns_searchpath: list of entries to go in the search line
#
# dns_disableforbuild: If there is no DNS available in the build
# environment, set this to delay the configuration
# 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=""

base_config_dns_disableforbuild="yes"

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

############
#
# Network Interface information
#
#
# networkifs: a list of interfaces to be defined,
# space seperated "le0 hme0".
# N.B. the sysidcfg interface will already be configured
#
# Logical interfaces should be defined using _'s rather
# than :'s.
#
# networkif_<ifname>: the details of the interface <if>
# "netname netmask hostname address"
#
# netname: arbritrary name for /etc/networks
# netmask: netmask of this if (e.g. 255.255.255.0)
# hostname: unique hostname (N.B. not multihomed)
# address: IP address of this interface
#
# For example:
#
# base_config_networkifs="ge0 ge0_1"
# base_config_networkif_ge0="bkp 255.255.255.0 me-bkp 192.168.1.0"
# base_config_networkif_ge0_1="bkp2 255.255.255.0 me-bkp2 192.168.2.0"
#

base_config_networkifs=""
base_config_networkif_le0=""

# N.B. Logical interfaces MUST use _ rather than : as illustrated below
base_config_networkif_le0_1=""

############
#
# IP Multipathing (Solaris 8+)
#
# IPMP default mode is automatic failback.
# To change this mode edit /etc/default/mpathd
#
# ipmp_networkifs: a list of interfaces to be defined under ipmp control
# a space separated list of pairs only
# e.g. "qfe0_qfe4 qfe1_qfe5"
#
# N.B. If the primary interface is used in an ipmp group, the
# system must be rebooted manually after installation to
# activate ipmp.
#
# N.B. Can only setup ipmp group with pairs of interfaces in one
# of the following configurations:
# active-standby failover:
# Set ipmp mode = s, and specify one logical
# hostname/ip address pair.
# failover with outbound load spreading:
# Set ipmp mode = l, and specify one logical
# hostname/ip address pair.
# active-active with outbound load spreading:
# Set ipmp mode = l, specify a second logical
# hostname/ip address pair for the second interface.
#
# ipmp_networkif_<if>_<if>: "netgroup mode test1 test2 mask hostname log-ip hostname2 log-ip2"
#
# details of the interfaces in the ipmp group
# e.g. networkif_ipmp_qfe0_qfe4
#
#
# netgroup: ipmp interface group name
# e.g. database-net
#
# ipmp mode: s = standby (failover only)
#
# ** test addresses are allocated last,
# ** first test address will be on the
# ** first virtual interface of the
# ** first physical adapter. Second
# ** test address will be on the second
# ** physical adapter.
#
# l = load spreading / active-active
#
# ** test addresses are allocated on
# ** first virtual interfaces on both
# ** the first and second physical
# ** adapters.
#
# To force the test addresses onto the physical
# adapters, use the suffix 'p' to the above
# modes, i.e. 'sp' or 'lp'. This is not
# recommended and may break certain applications.
#
# test1: ipmp test address1
# test2: ipmp test address2
#
# N.B. these addresses must not be used or
# placed in the hosts file
#
# mask: netmask for ipmp pair
#
# hostname: unique hostname for logical ip
#
# log-ip: logical ip address for first i/f of pair
#
# N.B. The following two parameters are for active-active
# configurations only. Do not specify them for an
# active-standby configuration.
#
# hostname2: unique hostname for logical ip
#
# log-ip2: logical ip address for second i/f
# of pair
# IPMP on Solaris 10.
# If you are running Solaris 10, you can optionally configure the
# system to have NO test addresses. In this case, the ipmp mode should be set
# to "ln" or "sn" depending on whether you want outbound load spreading or
# not and the 2 test addresses do not need to be privided.
#
# Examples:
# --------
#
#
# base_config_ipmp_networkifs="qfe0_qfe1"
# Outbound load spreading 2 hostnames, test on virtual interfaces.
# base_config_ipmp_networkif_qfe0_qfe1="db l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4"
# Outbound load spreading 1 hostname, test on physical interfaces.
# base_config_ipmp_networkif_qfe0_qfe1="db lp 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3"
# Failover, 1 hostname, test on physical interfaces.
# base_config_ipmp_networkif_qfe0_qfe1="db sp 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3"
# Failover, 1 hostname, no test addresses (Sol 10 only).
# base_config_ipmp_networkif_qfe0_qfe1="db sn 24 oracle-db 10.0.0.3"
#
#
base_config_ipmp_networkifs=""
base_config_ipmp_networkif_qfe0_qfe1=""

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

############
#
# NFSv4
#
# Set up the NFSv4 domain to prevent being prompted at first reboot.
# If not set, this will default to the entry in base_config_dns_domain,
# and if that is not set, to the value 'domain', which is the default
# in /etc/default/nfs
#
base_config_nfsv4_domain=""

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

base_config_productdir=""
base_config_patchdir=""

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

#
###############################################################################

@@@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.

←Older revision		Revision as of 09:01, 30 August 2006
Line 2:		Line 2:

	Contributor: Paul Juster		Contributor: Paul Juster
		+	With a significant help provided by the people @ [http://groups.yahoo.com/group/JETJumpStart/ JET Yahoo Group] & [mailto:JumpStart@yahoogroups.com JET Yahoo Group mail alias]

	== Overview of my set up ==		== Overview of my set up ==

@@ Line 13: / Line 13: @@
 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
+Do not assume any of the below applies to a SPARC JET client (there is a specific setting to enable a sparc client)
 == Download and Install the packages SUNWjet & documentation packages ==
@@ Line 81: / Line 81: @@
 (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
@@ Line 97: / Line 98: @@
 base_config_sysidcfg_default_route=192.168.0.254
 base_config_client_allocation="grub"
+</pre>
 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.
@@ Line 899: / Line 900: @@
 === JET Sparc_DHCP ===
-  > I now want to configure JET for a basic sparc DHCP and bootp build.
+  If you want to configure JET for a basic sparc DHCP and bootp build.
-−
-  > For Sparc DHCP do I just need to make the following changes…
+  For Sparc DHCP just make the following changes…
-−
- > Create a template with the
+  Create a template with the base_config_client_allocation equal "dhcp"
- > base_config_client_allocation equal "dhcp"
+  Edit /opt/SUNWjet/etc/Jumpstart.conf and add uname –i to JS_DHCP_VENDOR="SUNW.Ultra-5_10 SUNW.Ultra-30" to
- yep
+  reflect my wanting to use SPARC & DHCP.
- > edit /opt/SUNWjet/etc/Jumpstart.conf to add uname –i
- > to JS_DHCP_VENDOR="SUNW.Ultra-5_10 SUNW.Ultra-30" to
+  make_client will create the appropriate settings in dhcpmgr etc.
- > reflect my wanting to use SPARC & DHCP.
 === JET Sparc_Bootp ===
-  > For Sparc bootp do I just need to create a template
+  For Sparc bootp just create a template with the base_config_client_allocation equal "bootp"
- > with the base_config_client_allocation equal "bootp"
+  and make_client will create the appropriate settings in tftpboot etc.
- > And I assume make_client will create the appropriate
+=== Changing the media location ===
- > settings in tftpboot etc.
+<pre>
+  If you want to change media locations from my example of /export/install to say
- uh huh
- > I will not be able to test this for a week or so, as
+Update my “solaris locations” you will need to make JS_SOLARIS_DIR=/export/jumpstart
- > so far all my testing has been done using Vmware
+Only thing that matters is the solaris media locations. The JS_SOLARIS_DIR only affects the location of the media
- > locally on my laptop.
+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..
-=== Changing the media location ===
+</pre>