I need to create just a boot server for some SPARC boxes (with fixed
IPs and present in the hosts file) and am just reading thro the docs
for Jumpstart.
Have enabled tftpd I think
I have mounted the install DVD and am now here:
bash-3.00# ls /mnt/sol10/Solaris_10/Tools
Boot add_install_client rm_install_client
Installers dial setup_install_server
bash-3.00# mkdir /jumpstart
I am unsure what I should do next.
- maybe
cd /mnt/sol10/Solaris_10/Tools
./setup_install_server -b /jumpstart
not sure if -t <boot image path> is required.
Then I dont quite understand what I need to do to add a client for
booting - maybe
./add_install_client -e 00:03:ba:xx:xx:xx -i 192.168.1.12 -s
192.168.1.13:/jumpstart oxygen sun4u
Help if you can - appreciated!
Syd
You really need to download the manual and read it! The manual you need
was called something like "Advanced Installation Manual" the last time I
looked (that was three or four years ago and may have changed).
Very briefly, and perhaps too briefly, add_install_client sets up your
server to install Solaris on a particular machine. ISTR that you need
to prepare a file that says what sort of installation you want to do and
another file that has the host name, IP address, subnet mask, etc.
Go thou, and RTFM. It will probably save you a few hours of struggle!
Google around for Solaris jumpstart guides or how-tos.
Sunsolve has some good jumpstart troubleshooting stuff.
Once you've got things working, by all means read the manual.
Whether jumpstart is the right installation method for you is
another question.
--
John.
sydney...@yahoo.com wrote at 19.03.2009 14:17
> Hello,
>
> I need to create just a boot server for some SPARC boxes (with fixed
> IPs and present in the hosts file) and am just reading thro the docs
> for Jumpstart.
quite easy
> Have enabled tftpd I think
ok, but unnecessary because setup_install_server would enable it otherwise.
That's what you need:
<http://docs.sun.com/app/docs/doc/820-0179>
>
> Then I dont quite understand what I need to do to add a client for
> booting - maybe
> ./add_install_client -e 00:03:ba:xx:xx:xx -i 192.168.1.12 -s
> 192.168.1.13:/jumpstart oxygen sun4u
That's right, but not enough. Just read the doku, it's well explained there.
HTH,
Michael
Hi,
I can see where you are coming from with the RTFM and maybe jumpstart
is not right for me.
But I have read some fine manuals including the advanced install
guide. And I really do want to just have a boot server - need to
quickly load flash archive on 20 machines - and although booting from
CD and specifying the flash by hand does work just fine - there are
some boxes without a cd drive.
I have run
/mnt/sol10/Solaris_10/Tools/setup_install_server /jumpstart
./add_install_client -e 00:03:ba:xx:xx:xx -i 192.168.1.12 -s
192.168.1.13:/jumpstart oxygen sun4u
and then carried out a stop A, boot net, from oxygen:
but get error message "cannot open neither boot_archive nor miniroot"
I _think_ this is because there is a -t <install boot image path>
missing from my add_install_client
but I dont know where /mnt/sol10/Solaris_10/Tools/
setup_install_server /jumpstart has put the image.
Assistance with this gratefully received!!
Syd
Good.
> ./add_install_client -e 00:03:ba:xx:xx:xx -i 192.168.1.12 -s
> 192.168.1.13:/jumpstart oxygen sun4u
Where is "."? You should be in /jumpstart, not on the DVD any longer.
Why -s? The server knows where the code is. You don't need to give
this since you're running the command from a full server, not a boot
server.
> and then carried out a stop A, boot net, from oxygen:
> but get error message "cannot open neither boot_archive nor miniroot"
>
> I _think_ this is because there is a -t <install boot image path>
> missing from my add_install_client
> but I dont know where /mnt/sol10/Solaris_10/Tools/
> setup_install_server /jumpstart has put the image.
Shouldn't be necessary. It should find it. Does it do it when you
leave the -s bit off?
--
Darren
Some examples are here: http://docs.sun.com/app/docs/doc/817-5506/customjumpsample-1?a=view
http://docs.sun.com/app/docs/doc/817-5506/preparecustom-56440?a=view
seems to give detailed instructions. Links to flar's etc are off of
that page.
zfs jumpstart installations, may, be, present, here:
http://search.sun.com/docs/index.jsp?col=docs_en&locale=en&qt=zfs+jumpstart
Right. Useful for deploying a server that does the subnet-local stuff
if you're doing traditional jumpstart.
> Now I suspect that it has something to do with tftp, is there a test I
> can do to check that tftp is OK - I did enable it according to googled
> instructions - but a test was not included. I guess I should be able
> to pull back a file from the boot server to any client - each client
> already has solaris installed.
Why do you think TFTP would be the problem here. It probably is not.
> Please what would be an appropriate tftp test?
Please show the exact output you get from 'boot net'.
If you want, it's often useful to run 'snoop <client>' on the jumpstart
server while starting the client boot. You'll see the TFTP packets if
they begin. Either way, seeing what happens when the jumpstart ends can
be useful.
--
Darren
It's also helpful to pass the "-v" flag to the boot command. This
will provide a bit more information from the client side. The full
command looks like:
ok> boot net -v - install
I don't normally worry about it during jumpstart. The flag will show
modules as they load, but most JS problems happen before or after that
point. It's good if you get the Solaris banner, but then the machine
hangs before any jumpstart messages.
--
Darren
Usage: ./add_install_client [-i ipaddr] [-e ethernetid] [-s
server:path]
[-c server:path] [-p server:path]
[-n [name_server]:name_service[(netmask)]]
[-t install boot image path] client_name
platform_group
> had a good look at the docs suggested in this thread.
> I think I need to add a sysidcfg file - syntax is easy for the
> sysidcfg.
> add_install_client is not clear to me. the -p option which specifies
> where the sysidcfg field is located. Can I omit the -p option and put
> the sysidcfg in /jumpstart and this will be picked up ( Earlier I did
> a ./setup_install_server -b /jumpstart ) ?
I'm not sure if you can do this. The reason why there is an extra option
for sysidcfg file is that the name must exactly be sysidcfg - for all
jumpstart clients.
So you can use one path for your profile files (the clients are
identified in the rules.ok file) but if you need different sysidcfg
answers you have to use different subdirectories of, lets say
/jumpstart, for every sysidcfg file that should be different.
Michael
If you don't have a sysidcfg, you'll be dumped into an interactive
installer screen. If that's not what's happening, then that's not your
problem.
Can you show what happens after starting the boot?
--
Darren