Hi i'm tryin to set up a jumpstart to boot my client machine on the same subnet.Both machines are sun sparc( actully a server is Sunblade 150) and a client is (sunblade 20000) and i'm using Solaris9.My problem is whenever i issue a command boot net -install at client machine i got the timeout messages "Timeout waiting for ARP/RARP packet" and then finally it prints a warning message says that "boot will not enable cache" and requesting Internet address for (MAC address) and prompt to
Enter filename [kernel/sparcv9/unix]:
I tried to google around and found some suggestions that a client and server cant see each other.
Any work around on this problem?
Bavon

place the client MAC address on the server /etc/ethers

ex:

/etc/ethers

00:00:4b:3e:45:e2 192.168.1.1
00:00:56:3e:36:1f 192.168.1.2

Necronomicom,
Thanks for the reply.I already put my MAC address in /etc/ethers and even edited /etc/hosts, still client machine cant see the server.Don know wat do at this moment.

could it be something related to the rarp deamon?

Make sure your Jumpstart directory and OS image are NFS shared on your Jumpstart server and make sure your /tftpboot is shared and mounted on your boot server( if you use a bootserver that is seperate from your jump server) and make sure you can nfs mount it on client.
Make sure you did all the normal setup_install_server stuff and
make sure you did

Then you have to run the add_install_client with the options you want ( you have to tell it everything you want for that client) -

or add


to your /etc/bootparams on the server so that the client can access the OS part of the jumpstart -


The "Timeout waiting for ARP/RARP packet" is not an error it is getting the mac and and requesting an address - I have got the "Enter filename [kernel/sparcv9/unix]:" many times with our jumpstarts and what it means is the client cannot access the boot image or it does not know what bootserver to use - the above should help you check that -

This is just some real quick tips let me know if you need any more help - I do alot of jumpstarts

ADxD_7,
Thanks for your help,i'm still getting these timeout messages.
This is how i've set up my jumpstart.

1)Boot server(where OS image is installed)is located on machine "LA" in
/export/jumpstart/image.

steps:
cd /<cd mount>/Solaris_9/Tools
./setup_install_server /export/jumpstart/image

2)Configuration files( profiles,rules,sysidcfg,rules.ok,begin script,finish script,and check) are all located on the same machine "LA" under
/export/jumpstart/config

3) I share both my directories( image and config)
vi /etc/dfs/dfstab

share -F nfs -o ro,anon=0 /export/jumpstart/config
share -F nfs -o ro,anon=0 /export/jumpstart/image
shae -F nfs -o ro,anon=0 /tftpboot

4) I enable services
#svcadm enable nfs/server
#svcadm enable rarp
#svcadm enable tftp/udp6

5)Copy MAC address to /etc/ethers
e.g. 00:00:4b:3e:45:e2 192.168.1.1

6) i add the line below to my /etc/tftpbootparams

* install_config=XX.XX.XX.XX:/export/jumpstart

7)Adding client on the server
cd /export/jumpstart/image/Solaris_9/Tools
# ./add_install_client \
-e XX:XX:XX:XX:XX:XX \
-i XX.XX.XX.XX \
-s XX.XX.XX.XX:/export/jumpstart/image \
-c XX.XX.XX.XX:/export/jumpstart/config \
-p XX.XX.XX.XX:/export/jumpstart/config \
pino1 \
sun4u

8) On client side i issue
Ok boot net -install

Cool, well I would double check a few things ..

1. That you have set up the boot server

cd /<cd mount>/Solaris_10/Tools
./setup_installserver -b /export/boot

and - Make sure you share this (the /export/boot)(or /export/jumpstart/boot) -

2. Make sure when you do " share " command all of the shares show up( I have had it where the NFS was messed up) I would recommend just shareing out the whole /export/jumpstart directory instead of specifying the different dirs because " OS " and everything below it has to be shared

3.Make sure that the ip and hostname pair of the client is in your /etc/hosts like so

xxx.xxx.xxx.xxx hostname hostname.jump.cool.com

on the server -


4. Make sure that

* install_config=XX.XX.XX.XX:/export/jumpstart

is in your /etc/bootparams ( /etc/tftpbootparams doesnt matter)(you just need to make /tftpboot shared because add_install_client adds entrys into this and the client needs to be able to see it)

* OR * (dont do both - this is better than above) run the add_install_client with the options you said but also add

-t boot_image_path

where boot_image_path is the path to the shared boot image made above

e.g.
/export/boot

but I guess you only have to do that if you have it somewhere besides the ..TOOLS/ dir but I would do it anyway if wont hurt anything

-----

The issue is deffinatly that your machine cant see a boot image so make sure to check the above things -- and I may have given you some extra steps because here I am used to using a seperate boot server -- but it wont hurt anything


Let me know how it works out ---

Thanks ADXD_7,
This seems to be very challenging.I tried without success i'm still geting those timeout messages.
I share almost the whole jumpstart directory but don know why it behaves like this.
This is my what i get after typing "share" command at my boot server prompt

#cd /
#pwd
/
# share
- /export/jumpstart/image ro,anon=0 ""
- /export/jumpstart/config ro,anon=0 ""
- /tftpboot ro ,anon=0 ""
#

On client side i tried both options
1) ok> boot net -install

and second
2) ok> boot net -install -t /export/jumpstart/image


But was unseccessful,
Do u have a sort of step by step guide which you use and succed to jumpstart on sparc machines.

thanks,
Bavo

The command you are entering is wrong on the client.

It is boot net - install <- notice there is a space before the word install.

That is why is failing. Look at your original post.

Hope it helps,

J.

Thanks for all who replied on this thread.I finally installed my sparc machine.
So i think its worth to share these steps below and this link(http://www.codefund.com/506/client-f...r-5065316.shtm) with other users who might have the same problem.

****************************************
Normally this is a result of the bootparams not being able to get to the
install image.
'Timeout waiting for ARP/RARP packet...'

To solve the first problem:

1. Check how the dfstab(4) (/etc/dfs/dfstab on the install image NFS
server) looks:
share -F nfs -o ro,anon=o /jumpstart-dir

2. Run share(1M) command on the installed image NFS server, to make
sure it is shared properly.

3. Check /etc/bootparams file on the net install server. Look for
entries with incorrect boot path.

4. Make sure that /usr/sbin/rpc.bootparamd is running on the boot
server. If necessary, kill and restart it.

5. Check /etc/ethers on the boot server for duplicate or conflicting
entries
6. At OK prompt, run test net /test-net and/or watch net /watch-net to test the network connectivity

A workaround for the second problem is to check the nsswitch.conf(4)
file. If some of the entries point to NIS such as:

rpc nis files
hosts nis files
ethers nis files
bootparams filesnis

change all of these entries to files first:
rpc files nis
hosts files nis
ethers files nis
bootparams files nis
Note - You may have to manually update these files if they do not contain


info on the client machine you are trying to jumpstart.

Then remove the client with rm_install_client(1M), remove the contents of

tftpboot,

and re-add the client:
add_install_client -c /jumpstart-dir/profiles 'client name' 'arch'