trying to install solaris 10 on sun file v210

My problem is solved by updating the system to the latest available firmware which is

which is

OBP 4.22.28 2007/03/01 07:08

Lydia

lydia.hecka at 2007-7-28 18:51:59 >

I am using jet to do the jumpstart and the config file for jet is list below.

The install server is solaris 10 sparc

SunOS nereid 5.10 Generic_125100-10 sun4u sparc SUNW,Sun-Blade-1500

The version I am trying to install is 118855-33 (sol10-u3 - i believe). I have downloaded

the latest recommended patchset which should bring me to 118855-36 plus the latest

minor kernel patches.

nereid-root (482)>cat m1001

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

#

# Client template file

#

# Client:m1001 (derived from quintor.js)

# Created:Wed Mar 8 14:38:51 GMT 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

#

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

base_config_ClientEther=00:03:ba:60:36:0d

base_config_ClientOS="sol10_u3"

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

#

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

#

base_config_client_allocation="newboot"

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

#

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

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

#

# 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_UKfor Solaris 2.6

#en_GBfor 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=172.17.3.1

base_config_sysidcfg_netmask=255.255.0.0

base_config_sysidcfg_root_password="xxxxxxxxxxxx"

base_config_sysidcfg_system_locale="en_GB.ISO8859-15"

base_config_sysidcfg_timeserver=

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=

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

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

base_config_x86_console=""

base_config_x86_disable_acpi=""

base_config_x86_safetoreboot=""

#

#

#

#

#######

#

# Want to create your own custom profile ? if so, use this variable to

# reference a file relative to the Clients/<clientname> directory, otherwise

# fill in the other details below to get toolkit to create one for you.

#

base_config_profile=""

#

#######

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

#

# 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

#swaps1

#/vars5

#/usrs6

#/opts7

#

#at most one partition can have the size 'free' which denotes all the

#unallocated/spare space on a disk.

#

base_config_profile_cluster=SUNWCall

base_config_profile_usedisk=rootdisk.

base_config_profile_dontuse=""

base_config_profile_root=8192

base_config_profile_swap=4096

#

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

base_config_profile_s5_size=""

base_config_profile_s6_mtpt=""

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="/export/disk/1"

base_config_profile_s7_size="free"

#

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

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

#

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

base_config_profile_disk_c0t3d0s0_mtpt=""

base_config_profile_disk_c0t0d0s0_size=

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

#

# 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="SFWrpm SFWexpct SUNWzebrar SUNWa2psr SUNWmysqlr SUNWffiltersr SUNWopensslr SUNWserr SUNWsmbar SUNWa2psu SUNWant SUNWbison SUNWflexlex SUNWfreetype2 SUNWggrp SUNWgimpprint SUNWgm4 SUNWgnome-a11y-gok SUNWgnome-a11y-reader SUNWgnome-camera SUNWgnome-games SUNWgnome-img-editor SUNWgnome-img-viewer SUNWgnome-media-player SUNWgnome-project SUNWgscr SUNWgtar SUNWGtku SUNWhpijs SUNWimagick SUNWmozilla SUNWmoznspr-devel SUNWmysqlt SUNWmysqlu SUNWncft SUNWopenjade SUNWopensp SUNWopenssl-commands SUNWpsutils SUNWPython SUNWsmbac SUNWsmbau SUNWsmcmd SUNWTcl SUNWtexi SUNWTk SUNWwebminu SUNWwgetu SUNWzsh SUNWjavaapps SUNWmozapoc-adapter SUNWmozchat SUNWmozdom-inspector SUNWmozgm SUNWmozilla-devel SUNWmozjs-debugger SUNWmozmail SUNWmoznspr SUNWmoznss SUNWmoznss-devel SUNWmozpsm SUNWmozspell SUNWopenjade-devel SUNWopenjade-root SUNWopenjade-share SUNWopensp-devel SUNWopensp-root SUNWopensp-share SUNWseru SUNWserweb SUNWsfinf SUNWsfman SUNWsmdoc SUNWzebrau SUNWpostgr SUNWpostgr-contrib SUNWpostgr-docs SUNWpostgr-jdbc SUNWpostgr-libs SUNWpostgr-pl SUNWpostgr-server SUNWpostgr-server-data SUNWpostgr-tcl"

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

#

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

base_config_networkif_beg1="data 255.255.0.0 d1001 172.18.3.1"

# 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

#

# Example:

# --

#

# base_config_ipmp_networkifs="qfe0_qfe1"

# base_config_ipmp_networkif_qfe0_qfe1="database-net l 10.0.0.1 10.0.0.2 24 oracle-db 10.0.0.3 apache 10.0.0.4"

#

#

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

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

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

#

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

#

# productdiris where to find the products. This should be an NFS style

#path, i.e. 192.168.1.1:/export/install but if the server

#is the JumpStart server, then it should just be specified

#as a normal path.

#

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

#

base_config_debug_jumpstart_postinstall=""

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

#

# Product:Custom

#

# Synopsis:The custom product can install packages and patches that

#would not otherwise be included by the standard

#installation products.

#

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

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

#

# Which additional packages are to be installed

# (by default, these get added during the main Solaris installation phase)

#

# O.S. Specific versions:

#as a side effect, if a directory exists under the package dir named

#after the OS, (uname -r), the subdirectory will be used instead of the

#main package directory

#

#i.e /export/install/pkgs/custom/sparc/5.8 takes preference over

#/export/install/pkgs/custom/sparc for a Solaris 8 box

#

# Package Response files:

#If a custom package needs a response file, create a directory called

#/opt/jet/Clients/<clientname>/responses

#and put the response file in to it, named the same as the package.

#

#i.e. for a package called Fred, on client1, use pkgask to create

#pkgask -r /opt/jet/Clients/client1/responses/Fred Fred

#

# (Space seperated list of packages)

#

custom_packages=""

#

# Custom packages at subsequent boots

#

custom_packages_1=""

custom_packages_n=""

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

#

# Which additional patches are to be installed

# (by default, these get added during the main Solaris installation phase)

# (Space seperated list of patches)

#

custom_patches=""

#

# Custom patches at subsequent boots

#

custom_patches_1=""

custom_patches_n=""

#

# Custom patch sets... create a directory in the patch directory named after

# the set, and put a patch_order file in it, along with the patches...

# (Space seperated list of patch set names)

#

# N.B. as a side effect, if a directory exists under the patch set dir named

#after the OS, (uname -r), the subdirectory will be used instead of the

#main patchset directory

#i.e /export/install/patches/patchset/5.8 takes preference over

#/export/install/patches/patchset

#

custom_patchsets=""

#

# Custom patchsets at subsequent boots

#

custom_patchsets_1=""

custom_patchsets_n=""

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

#

# Search paths

#

# The files and scripts sections below will look for source files relative

# to the Clients/<clientname> directory. If you wish to look in other places

# for files, please fill out the search path option below. Items in the

# search path are relative to the Clients/<clientname> directory, since the

# client has no knowledge of the filesystem layout of the server

#

# e.g. for a client 'fred', the default location for all custom files/scripts

#is /opt/jet/Clients/fred

#

#if the search path was set to "../common" then the installation routines

#would look first in Clients/fred then

#Clients/fred/../common (or Clients/common in this case)

#

# Search path is a space separated list of places to search

#

#THE SEARCHPATH IS ONLY VALID FOR files & scripts. NOT PACKAGES/PATCHES!

#

custom_search_path="../common.files"

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

#

# Files to be copied to the client. The filenames must be of the form

#

# filename1:[a|o]:filename2

#

# Where filename1 is the name of the source file in the

#/opt/jet/Clients/<clientname> directory

#filename2 is the full path of the file on the installed client

# and the middle option is whether to a - append, or o - overwrite the file

#

# (by default, these get added during the main Solaris installation phase)

#

# (Space seperated list of tuples)

#

# N.B. Please see section above regarding where to place the source files

#

# N.B. (2):

#appending to /etc/hosts is a special case; instead of just appending

#the file, the module will do an 'intelligent merge' of the new hosts

#file with the existing one.

#

#custom_files="hosts:a:/etc/hosts"

#

#custom_files="system:a:/etc/system"

custom_files=""

custom_files_1="NISHost:a:/etc/inet/hosts QuintorNFS:a:/etc/vfstab authorized_keys:o:/.ssh/authorized_keys SGEServices:a:/etc/services"

#

# Custom files at subsequent boots

#

custom_files_n=""

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

#

# Scripts to be run on the client at the end of the build

#

# The scripts must be placed in the directory

#/opt/jet/Clients/<clientname>

# and will be copied to the client.

#

# Note: we don't allow you to run custom scripts during the Jumpstart

# phase because its kinda dangerous.

# If you need to do this, the best way is to create

# your own custom module to do this.

#

# Custom scripts at subsequent boots

#

custom_scripts_1="DurhamUni_PostInstall.ksh fixup_ssh"

custom_scripts_n=""

#

# Special JumpStart 'Begin' phase scripts

#

# If you need to run scripts in the 'begin' phase of the JumpStart, you

# can supply them here. Please note, that in the 'begin' phase, the

# new OS has not been installed and the majority of the OS running will

# be read-only from the JumpStart server.

#

custom_scripts_b=""

#

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

nereid-root (483)>

lydia.hecka at 2007-7-28 18:51:59 >