From: Ciaran Luttrell (ciaran.luttrell@druid-dns.com)
Date: Wed Aug 25 2004 - 09:50:31 EDT
Hi there,
This is my first time using this mailing list so please excuse any mistakes.
Here is a description of my problem which I need to have resolved by tomorrow
evening.
I have successfully set up a jumpstart server on a Sun Ultra 5 which is being
used to jumpstart a training lab of Sun Blade 1500's with Solaris 8 05/03. I
have jumpstarted all the machines before without using a sysidcfg file,
simply because I wasn't aware I could use one.
I have since added the following sysidcfg in an attempt to make the
installation completely unaided. I have added it to the same directory as
the custom jumpstart config files, also shown below.
SYSIDCFG FILE
language=US-English
system_locale=en_IE
timezone=GMT
network_interface=primary {netmask=255.255.252.0
protocol_ipv6=no}
security_policy=NONE
#root_password=luttrell
name_service=DNS{
domain_name=training.eirteic.cobh.office
name_server=192.168.5.5
search=training.eirteic.cobh.office,eirteic.cobh.office,cobh.office}
timeserver=localhost
keyboard=ATKBD {layout=US-English}
RULES FILE - appropriate part
##
# Ultra 10s and Sun Blade 1500's
karch sun4u - training_profile2 -
karch any - training_profile2 -
TRAINING_PROFILE2
install_type initial_install
system_type standalone
cluster SUNWCXall
geo W_Europe
partitioning explicit
filesys c0t0d0s0 free /
filesys c0t0d0s1 2048 swap
I then re-added one of the clients using the following command as advised by
the Sun Advanced Intallation guide.
./add_install_client -c jumpstart:/jumpstart -p jumpstart:/jumpstart alfred
sun4u
jumpstart:/jumpstart is the host and directory containing both the config
files and the sysidcfg file.
This updates the bootparams file, show below.
freeze root=jumpstart:/export/install/Solaris_8/Tools/Boot
install=jumpstart:/export/install boottype=:in
install_config=jumpstart:/jumpstart rootopts=:rsize=32768
bladetest root=jumpstart:/export/install/Solaris_8/Tools/Boot
install=jumpstart:/export/install boottype=:in
sysid_config=jumpstart:/jumpstart install_config=jumpstart:/jumpstart
rootopts=:rsize=32768
alfred root=jumpstart:/export/install/Solaris_8/Tools/Boot
install=jumpstart:/export/install boottype=:in
sysid_config=jumpstart:/jumpstart install_config=jumpstart:/jumpstart
rootopts=:rsize=32768
Now, finally, here's my problem.
When I proceed to do a boot net - install from the client Alfred, it finds and
uses the sysidcfg file like I had hoped. Brilliant, except now it no longer
can find the jumpstart directory containing the rules file, even though this
hasn't changed.
Here's what it says on the console:
Searching for jumpstart directory...
not found
Warning: Could find matching rule in rules.ok
If I use the add_install_client script again so it will not use the sysidcfg
file, ie "./add_install_client -c jumpstart:/jumpstart sun4u", it will find
the rules file, however I have to manually enter the settings in the sysidcfg
file. I really want to avoid this as the training lab has 18 machines and
need to be jumpstarted regularly, in fact tomorrow again.
Help Please!
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:29:21 EDT